Enhanced Restful Operations

ABSTRACT

A batch of CRUD operations can be coupled with the resource discovery operation and directly conducted on the matched resources, without initiating new CRUD requests. New functionality at the Originator and Receiver can differentiate the resources for which criteria matching is applied from the resources included in the discovery/filtering results. Enhanced functionality at the Originator and Receiver can combine discovery with RESTful operations targeting a resource set different than but related the discovered resources. Other enhancements may be used to request discovery of resources in a specified relationship to those matching a filter, or to request group formation based on the result.

CROSS-REFERENCE TO RELATED APPLICATIONS

This Application is a continuation of U.S. patent application Ser. No.17/245,246, filed on Apr. 30, 2021 which is a continuation of U.S.patent application Ser. No. 15/762,263, filed Mar. 22, 2018, now U.S.Pat. No. 11,019,155, which is a National Stage Application filed under35 U.S.C. § 371 of International Application No. PCT/US2016/053342 filedSep. 23, 2016, and which claims the benefit of U.S. Provisional PatentApplication Ser. No. 62/222,536, filed Sep. 23, 2015, the disclosures ofwhich are hereby incorporated by reference as if set forth in theirentireties.

BACKGROUND

In recent years M2M solutions enabling machines/devices to communicatewith each other have been developed for the healthcare sector, theenergy sector, and the automotive sector. The next step of optimizationis to provide solutions integrating machines and things from differentsectors on the same platforms.

For this purpose, a single set of standards defining a horizontalplatform for the exchange and the sharing of data among applicationsindependent of industry sectors has been initiated by oneM2M. “oneM2M iscreating a distributed software layer—like an operating system—which isfacilitating that unification by providing a framework for interworkingwith different technologies.” (quoted from “The Interoperability Enablerfor the Entire M2M and IoT Ecosystem”, OneM2M White paper) Thisdistributed software layer is implemented in a common service layer thatsits between the M2M applications at application layer 104 and thecommunication hardware/software that provides data transport at thenetwork services layer 106 (See FIG. 1).

The Service Layer 106 is enabled functionally by Common ServicesFunctions (CSFs). A group of CSFs may be instantiated as a group onCommon Services Entities (CSEs). An example CSE 202 is shown in FIG. 2.Examples of CSFs are described in the following paragraphs.

Application and Service Layer Management CSF 204 provides management ofAEs and CSEs. This includes capabilities to configure, troubleshoot andupgrade functions of the CSE, as well as to upgrade the AEs

Discovery CSF 206 searches for information about applications andservices based on a filter criteria. Additional information on this CSFis described below.

Registration CSF 208 provides the functionality for AEs (or other remoteCSEs) to register with a CSE. This allows the AEs (or the remote CSE) touse the services of the CSE.

Communication Management/Delivery Handling CSF 210 providescommunications with other CSEs, AEs and NSEs. This CSF decides at whattime and which communication connection for delivering communicationsand if necessary and allowed, to buffer communications request so thatthey can be forwarded at a later time.

Group Management CSF 212 provides for the handling of group relatedrequests. Enables an M2M system to support bulk operations on multipledevices, applications, etc.

Security CSF 214 provides security functions for the service layer, suchas access control including identification, authentication, andauthorization.

Data Management and Repository CSF 216 provides data storage andmediation functions (collecting data for aggregation, re-formattingdata, and storing data for analytics and semantic processing).

Location CSF 218 provides the functionality to enable AEs to obtaingeographical location information.

Service Charging & Accounting CSF 220 provides charging functions forthe service layer

Device Management CSF 224 provides management of device capabilities onM2M gateways and M2M devices.

Network Service Exposure, Service Execution and Triggering CSF 226manages communications with the Underlying Networks for accessingnetwork service functions

Subscription and Notification CSF 228 provides functionality to allowfor subscribing to an event and to be notified when this event occurs.

The oneM2M architecture provides for a CSE 202 to interface through theMca, Mcc (and Mcc′), and Mcn reference points (respectively) withApplication Entities (AE) 230; other CSEs; and Network Service Entity(NSE) 232, i.e. the underlying network.

oneM2M uses two architectural approaches to develop the service layerarchitectural specifications: Resource Oriented Architecture (ROA) shownin FIG. 3A and Service Oriented Architecture (SOA) shown in FIG. 3B.

The ROA architecture is detailed in oneM2M-TS-0001, oneM2M FunctionalArchitecture V2.1.0. It is developed around resources and the operationsperformed by CSFs to enable their functionality. Resources arearchitectural elements uniquely addressable via Uniform ResourceIdentifiers (URIs).

Resources may be viewed as a hierarchical trees, emanating from a base,with a number of relationships defined among them. For example, aresource may contain child resource(s) and attribute(s), the childresource having a containment relationship with a parent resource.Therefore, the parent resource representation contains references to itschild resources(s). The lifetime of a child-resource is limited by theparent's resource lifetime.

Attributes are architectural elements that store information of theresource. oneM2M defines a set of attributes common to all resources,and others are specific to individual resources and are referred to as“resource specific attributes”. Resources located at one CSE (referredto as Hosting CSE) may be announced to remote CSEs, and these arereferred to “announced resources.” The announced resources may containattributes of the original resource as well as their own attributes.Synchronization between the original resource and the announcedresource, is the responsibility of the Hosting CSE.

The SOA architecture is detailed in oneM2M-TS-0007, Service ComponentArchitecture V0.8.1. It is developed around the services themselves andmay be used in legacy deployments that are not RESTful based. The SOAservice layer contains various M2M services which may be grouped intoservice components. In addition to the existing reference pointsintroduced in the ROA architecture, the SOA architecture introduces theinter-service reference point Msc.

The general flow that governs the information exchange in oneM2M isdescribed in oneM2M-TS-0001, oneM2M Functional Architecture V2.1.0 andis based on the use of Request and Response messages within acommunication procedure shown in FIG. 4. An originator 402 sends arequest message to receiver 404 and the receiver 404 responds withresponse message.

This procedure applies to communications between AEs and a CSE (over theMca reference point) as well as among CSEs (over the Mcc referencepoint). Depending on the operation carried by the messages, theseprocedures may manipulate information in standardized resourcerepresentations via RESTful methods such as CREATE, RETRIEVE, UPDATE,and DELETE.

Both the request and response messages are specified, and containmandatory, optional or conditional parameters. Table 1 is a list ofrequest parameters with brief descriptions, full descriptions can befound in oneM2M-TS-0001, oneM2M Functional Architecture V2.1.0.

TABLE 1 Request Parameter List Request Parameter Criticality DescriptionTo Mandatory Address of the target resource or target attribute for theoperation From Mandatory Identifier representing the OriginatorOperation Mandatory Operation to be executed: Create (C), Retrieve (R),Update (U), Delete (D), Notify (N). Request Identifier Mandatory IDenabling tracking of Requests and corresponding Responses ContentConditional (C) content of the new resource to be created based on (U)content to be replaced in an existing Operation: resource Mandatory (N)notification information for C, U, N Optional for: Optional (R) list ofattributes to be retrieved for R Resource type Conditional, Resourcetype for the resource to be created. Mandatory only for C Role OptionalOriginator role to be used in role based access control OriginatingTimestamp Optional Originating timestamp of when the message was built.Request Expiration Optional Indicates when the request messagesTimestamp (including delay-tolerant) should expire Response ExpirationOptional Indicates when the response messages Timestamp (includingdelay-tolerant) should expire Response type Optional Indicates what typeof response shall be used. Options are: nonBlockingRequestSynch,nonBlockingRequestAsynch, blockingRequest Result Content OptionalIndicates what the expected components of the result are. Options are:attributes, hierarchical-address, hierarchical-address + attributes,attributes + child-resources, child-resources, attributes +child-resource- references, child-resource-references, nothing,original-resource Result Persistence Optional Indicates the duration forwhich the address containing the responses is to persist. OperationExecution Optional Indicates the time when the specified Time operationis to be executed by the target CSE Event Category Optional Indicatesthe event category that should be used to handle this request intransit, such as: immediate, bestEffort, latest Delivery AggregationOptional Enables aggregation of one or more request for delivery to thesame CSE(s), depending on policies Group Request Optional Identifieroptionally added to group requests Identifier that is to be fanned out,in order to detect loops and avoid duplicated operations. FilterCriteria Optional Conditions for filtered retrieve operation aredescribed in the next section it is used for resource discovery andgeneral retrieve, update, delete requests. Discovery Result OptionalIndicates the preference of the Originator Type for the format ofreturned information in the result of the operation. Options are:Hierarchical addressing, non-Hierarchical addressing

The use of some of the request parameters above, which play an importantrole in discovery operations, is detailed in the following section.

Similarly, the table 2 provides a list of response parameters with briefdescriptions, full descriptions can be found in oneM2M-TS-0001, oneM2MFunctional Architecture V2.1.0.

TABLE 2 Response Parameter List Response Response Response ResponseResponse Response Code = Code = Code = Code = Code = Code = Responsemessage successful: successful successful: successful successfulunsuccessful parameter/success Response: Operation = Operation =Operation = Operation = Operation = Operation = or not Code = ACK CreateRetrieve Update Delete Notify C, R, U, D or N Response Code - M M M M MM M successful, unsuccessful, ack Request Identifier - M M M M M M Muniquely identifies a Request message Content - to be O O M O O N/A Otransferred (address of (The (the (The (The (Additional <request>address retrieved modified content error info) resource and/or theresource attributes actually resource for a content of content or eitherdeleted) non-blocking the created aggregated updated, request) resource)contents of deleted or discovered new) resources) To - the identifier OO O O O O O of the Originator or the Transit CSE (non-blocking request)From - the O O O O O O O identified of the Receiver Originating O O O OO O O Timestamp - when the message was built Result Expiration O O O O ON/A O Timestamp - when the message expires Event Category - O O O O O OO what event category shall be used for the response message StatusCode - (e.g. O O O O O O O authorization timeout, etc.)

Resource discovery is a process by which an entity (referred to as theOriginator 402) searches for information about applications and servicescontained in attributes and resources. In oneM2M, the Originator 402 ofa resource discovery can be either an AE or a CSE, and targets a rootresource at a Receiver CSE 404′ where the search is to start.

The content of the search result depends on some of the Filter Criteriaby matching certain search parameters (e.g. based on resource type,resource creation time, resource size, etc.) . . . Other Filter Criteriaparameters (e.g. limit), along with some operation parameters (e.g.Discovery Result Type) play a role in the way the content of the searchresult is provided back to the Originator 402. The discovery operation,just like the CRUD ones, is subject to the access control policy at theReceiver CSE 404′—that is, does the Originator 402 have “DISCOVER”access rights.

The complete list of search parameters is provided in Table 3 and it isbased on Table 8.1.2-1 in oneM2M-TS-0001 (oneM2M Functional ArchitectureV2.1.0). However, we distinguish here between filter criteria providedfor matching and those with other, such as specifying the type ofcriteria usage, or the way the results are returned. These parametersmay be combined by relational operations to create compound searchcriteria.

TABLE 3 Resource Discovery Filter Criteria Search Parameter Resourcematching if: createdBefore It was created before createdBeforecreatedAfter It was created after createdBefore modifiedSince It hasbeen modified since modifiedSince unmodifiedSince It has not beenmodified since unmodifiedSince stateTagSmaller It has state ag attributesmaller than stateTagSmaller stateTagBigger It has stateTag attributelarger than stateTagSmaller expireBefore It has expirationTime attributebefore expireBefore expireAfter It has expirationTime attribute afterexpireAfter labels It has labels attribute matching labels searchparameter. The labels are tokens used as keys for discovery purposesresourceType It is of type resourceType sizeAbove The contentSizeattribute of the <contentInstance> resource is equal to or greater thanthe sizeAbove value sizeBelow The contentSize attribute of the<contentInstance> resource matches the contentType value contentType ThecontentInfo attribute of the <contentInstance> resource matches thecontentType value attribute It has the corresponding matching resourceattribute Filter criteria (others) Role: limit This parameter is notused as search criterion, rather as in formatting/limiting the way thesearch result is returned filterUsage This parameter is not used assearch criterion, rather for indicating the use of the filter criteriafor discovery purposes

In oneM2M ROA the resource discovery is implemented using a RETRIEVEmethod, using filterUsage to indicate to the Receiver CSE 404′ todistinguish between a resource discovery operation and a genericretrieve operation.

A generic resource discovery procedure is shown in FIG. 5. TheOriginator 402 issues the Resource Discovery Request (Step 001) to theReceiver CSE 404′, trgeting specific child resources of resource<CSEBase>/<aeO1>. The Receiver CSE 404′ processes the request andreturns the appropriate list of discovered resources. The Receiver CSE404′ may limit the discovery result according to the DISCOVER privilegesof the discovered resources, and may change the filter criteriaaccording to its own local policy. If the full list of discoveredresources cannot be returned, the Receiver CSE 404′ will warn theoriginator 402 (with a flag). The Resource Discovery Response (Step 003)includes a list of addresses of the resources that match the FilterCriteria. It is the responsibility of the Originator 402, if needed, toretrieve the resources pointed to by the addresses.

SUMMARY

Batches of CRUD operations can be coupled with the resource discoveryoperation and directly conducted on the resource discovery outcome,without initiating new CRUD requests.

New functionality at the Originator and Receiver can differentiate theresources for which criteria matching is applied from the resourcesincluded in the discovery/ filtering results. An Originator can requestthat the resource discovery outcome be provided in a Filtering Result.The Filtering Result may be different than but related to the MatchedResource Set that fulfills Originator specified Filter Criteria. Therelation between the resources in the Filtering Result and those in theMatched Resource Set can also be specified by the Originator.

Enhanced functionality at the Originator and Receiver can link RESTfuland discovery operations. An Originator can request an operation on aTarget Resource Set. The Target Resource Set may be different than butrelated to a set of discovered resources (Filtering Result) based onOriginator discovery request. The relation between the resources in theTarget Resource Set and those in the Filtering Result can also bespecified by the Originator.

Enhanced Filter Criteria, such as to discover resources that have aparent or a child that match certain filter criteria, can be used.

Enhanced Filter Directives can for instance be used to request creationof a group for the resources matching the filter criteria, or to specifythe relation between Filtering Result and Matched Resources.

Enhanced Exception Handling can for instance be used to change theReceiver behavior, including the CRUD operation to be performed, whencertain conditions occur, based on Originator request.

The new parameters and processing of RESTful operations introduced canenable further new or enhanced functionality as follows:

-   -   Ability to request resource discovery to be followed by a CREATE        operation on the discovered resources, with processing only at        the Receiver and without back and forth messaging between the        Originator and Receiver    -   Ability to request resource discovery to be followed by an        UPDATE operation on the discovered resources with processing        only at the Receiver and without back and forth messaging        between the Originator and Receiver    -   Ability to request resource discovery to be followed by a DELETE        operation on the discovered resources with processing only at        the Receiver and without back and forth messaging between the        Originator and Receiver    -   Ability to provide different targets for the discovery procedure        and for the CRUD operation, although requested using the same        message    -   Ability to enhance the discovery operation or the filtering        performed before CRUD operations, by using conditions to be        matched at various levels of a resource tree    -   Ability to specify a difference/ relationship between resources        which get matched based on given criteria and the resources        composing the filtering/discovery result    -   Ability to specify a difference/relationship between the        resources composing the filtering/discovery result and those        targeted by the CRUD operations, e.g. by using resource        relationships such as Parent/Child, semantic descriptor, etc. in        determining of the operation target from the filtering/discovery        result.    -   Ability to request the creation of a group consisting of the        matched or filtered resources of a discovery operation.    -   Ability to request changes in the operation to be performed when        certain conditions/exceptions occur.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter. Furthermore,the claimed subject matter is not limited to limitations that solve anyor all disadvantages noted in any part of this disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

A more detailed understanding may be had from the following description,given by way of example in conjunction with accompanying drawingswherein:

FIG. 1 is a diagram of an oneM2M layered model.

FIG. 2 is a diagram of Common Services Functions.

FIG. 3A is a diagram of a Resource Oriented Architecture (ROA) oneM2MFunctional Architecture.

FIG. 3B is a diagram of a Service Oriented Architecture (SOA) oneM2MFunctional Architecture.

FIG. 4 is a diagram of general communication flow in oneM2M.

FIG. 5 is a diagram of an oneM2M general resource discovery procedure.

FIG. 6 is a diagram of a TaskManager use case.

FIG. 7 is a diagram of a use case flow with existing oneM2M operations.

8A-B is a diagram of a use case flow with existing oneM2M operations,using group functionality.

FIG. 9 is a diagram of a call flow for generic enhanced operations.

FIG. 10 is a diagram of an example call flow using enhanced CREATEoperation for the TaskManager use case.

FIG. 11 is a diagram of a generic call flow for the processing examples.

FIG. 12A-B is a diagram of a request processing flow chart.

FIG. 13 is a diagram of a Graphical User Interface of one embodiment.

FIG. 14A is a diagram of a M2M/ IoT/WoT communication system thatincludes a communication network.

FIG. 14B is a diagram of an illustrated M2M service layer in the fielddomain that provides services for the M2M application, M2M gatewaydevices, and M2M terminal devices and the communication network.

FIG. 14C is a diagram of an exemplary device that may be used toimplement any of the network nodes described herein.

FIG. 14D is a block diagram of a computer system or server that may beused to implement any of the network nodes described herein.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

Abbreviations

AE Application Entity

App Application

ACP Access Control Policy

ASN Application Service Node

CRUD Create, Read, Update, and Delete

CSE Common Service Entity

CSF Common Service Function

DIS Discovery

DMR Data Management and Repository

HW/SW Hardware/Software

IN Infrastructure Node

IoT Internet of Things

M2M Machine-to-Machine

MN Middle Node

ROA Resource Oriented Architecture

SOA Service Oriented Architecture

URI Uniform Resource Identifier

Definitions

Common Service oneM2M term for an instantiation of a set of CommonEntity (CSE) Service Functions. Common Service oneM2M term for a ServiceCapability. Function (CSF) Capabilities/Functionalities that reside inthe common Service Layer. Hosting CSE Can be CSE which hosts variousresources (oneM2M name for a Hosting Node) Hosting Node Can be an M2MService node which hosts various resources. The hosted resources can beaccessed and subscribed by other M2M entities. M2M Entities Can be anynode that participates in M2M communications, in both field andinfrastructure domains M2M Service Can be a network node hosting aservice layer Node supporting one or more service capabilities for M2Mcommunication. Middle Node Can be the CSE in a middle node. CSE MiddleNode Can be a node between a field domain M2M entity and aninfrastructure node or entity Originator Can be the entity thatinitiates of a Request message for a RESTful operation. For example, theCSE where an Originator is trying to perform a resource discovery viaRETRIEVE. Service Can be a specific type of service supported by aCapability service layer Service Layer Can be a software middlewarelayer that sits between M2M applications and communication HW/SW thatprovides data transport. It can provide commonly needed functions forM2M applications across different industry segments Receiver Can be anentity that receives a Request message with a RESTful operation, it canprocess it and send a corresponding Response message

Use Case: Industrial TaskManager

FIG. 6 depicts an industrial floor 600 with a variety of fixedmachinery, mobile vehicles and robots as well as movable tools(generically termed “equipment”). There are a variety of sensors on themachines, vehicles, tools, robots and on the floor. People are alsomoving through the area and accomplishing individual tasks.

The sprawling floor has multiple gateways which communicate with theequipment providing services of various levels of complexity. For anexample using an oneM2M-based platform, the gateways map to MN-CSEs andthe equipment to AEs (e.g. AE1, 2 . . . or AEx, y, z . . . ) residing oneither ASNs or ADNs registered to the nearest gateway. As such, anindividual MN might host the sensor measurements provided by a varietyof ambient sensors, as well as the resources necessary to control staticand complex machines such as automated milling machines or lathes.Nomadic robots also register to the nearest gateway after transitions.The M2M platform providing services to the factory and integrating theMN-CSEs also provides location and semantic services. For example, itmaintains location, operational status, maintenance status, etc.information for each piece of equipment registered via correspondingresources. In this case we assume the location and maintenance statusare maintained via labels applied to the relevant resources.

A mechanic has been performing maintenance in one of the floor sectorsand wants to find the units in the area when they stop, in order toperform an operation. For example he needs to check the physical statusof several components/items (e.g. wheels, bearings, accumulated debris),which might be different depending on the equipment type. He has accessto a mobile device with rich capabilities, which connects to the Wi-Finetwork of the industrial complex and registers itself to the nearestgateway (MN-CSE1) 602.

For this job, the mechanic uses a “TaskManager” application (AE_tm) 604which searches for any equipment ready for his operation and subscribesto the operational status information of the relevant devices. Thesubscriptions are targeted at equipment in the vicinity of the mechanicwhose maintenance is not current. It is assumed that location andmaintenance status are discoverable via labels (i.e. specializedresource attributes) applied to the relevant resources. The TaskManageraccomplishes this functionality by issuing a discovery request messageto the gateway (MN-CSE1 602) with the relevant search criteria (e.g.label=Sector#42 && label=maintenanceNotCurrent) and based on thereturned results, application creates a subscription notification to theoperational status (e.g. Off, Idle, Running). The gateway, which handlesseveral sectors, returns a list of all registered equipment in themechanic's vicinity and creates subscription to the operational statuscontainer.

As soon as the TaskManager AE_tm 604 is notified about a piece ofequipment that is idle or off, it retrieves additional details such asthe equipment type (static vs. not), expected idle time period, etc.When the mechanic updates his own status as available, the TaskManagerdirects him to the next equipment to be serviced and could provide atask checklist customized for the particular piece of equipment.

Owing to the dynamic nature of the operational status (machine mightbecome available and then busy again before being serviced), it is moreefficient to subscribe to the operational status, rather than regularlyperforming discovery based on the value of the operational status. Thiswill ensure that discovery requests will be minimized.

Also, there may be no available tasks at certain times if all equipmentin vicinity has been serviced, if none is idle or predicted to be idlefor a long time or if those available have changed positions. In any ofthese situations the TaskManager may initiate a new discovery (either onits own or at the mechanic's prompting) with different parameters suchas a new location.

To provide for this scenario in a current oneM2M implementation, theTaskManager AE_tm 604 application could perform a Discovery Request tofind equipment in the area, followed by a subscription creation based onthe discovery results. If the discovery returns a large number of piecesof equipment (e.g. N), it is followed by a large number of CREATErequests, as depicted in FIG. 7

If AE_tm 604 uses the oneM2M group creating mechanism, the group will becreated literally for a very limited amount of time and for very fewoperations, after which it should be deleted, as depicted in FIG. 8A-B.This is a naïve use of the group operation, for which the mechanismscurrently provided have not been optimized.

These mechanisms are therefore not optimal because of the overhead ineither the amount of messaging required and/or the number of short-livedgroups (with very limited use) created. While this use case exemplifiesthe CREATE operation, the issue is valid for all CRUD operations.

Another problem would be posed if the labels used for criteria matchingwould have been applied by different management applications at variouslevels throughout the resources tree. For example if the sector label isapplied to a <location> child container while the maintenance statuslabel has been applied to the <AE> parent resource. Current mechanismsproviding filter criteria to be matched against the same resourceresults in limitations in the usefulness of the results which may beobtained through any single discovery request.

Sometimes the procedure used by the TaskManager may discover machinesalready subscribed to, for example if the machine has been moved from apreviously serviced sector before having the maintenance updateperformed. In this case the TaskManager may want to mandate that theCREATE operation results in an update of the existing resource, ratherthan in the creation of a new resource with a changed name.

At the same time, other applications using the same gateway may requiredifferent processing of a similar case. For example when attempting tocreate a new resource and there is an existing child resource with thesame name, other application may need the existent resource to bedeleted and a new one with the same name and the new content to becreated. However, in general processing of such conditions or exceptioncases relies on default processing at the Receiver 404. This means thatcurrently no differentiation may be achieved in exception/ conditionhandling at the Receiver 404

Currently RESTful procedures target the execution of CRUD (Create,Retrieve, Update, and Delete) operations and may also allow for checkingthat certain criteria or conditions occur.

There are many use cases involving CRUD operations which target theresult of a discovery request and as such require separatesub-procedures and steps: some for performing the discovery and othersin execution of the CRUD operations on the resources provided by thediscovery step. As a consequence of a discovery resulting in a set (morethan one) of resources, several separate request/response procedures areneeded for executing the operation on each resource in the set, or groupcreation is needed.

The special procedures optimized for group operations do provideimproved messaging efficiency which is very useful for cases in whichthe same set of resources requires further handling as a group. Thereare however special cases in which creating persistent groups ofresources based on discovery results is not needed. These are cases whenthe result set validity is limited in time (very soon another discoveryoperation with the same parameters will yield different results) or whenthere is a limited number of operations to be performed on the resultset (possibly one).

In many cases, once an initial resource tree structure has beendiscovered, the discovery operation is used for search and filtering inpreparation of future operations. The existing procedures requiringsequential messaging and processing result in inefficiencies becausethey do not take advantage of resource tree information alreadyavailable at the Originator 402 before it performs some searches.Similarly, the Receiver 404 obtains information separately for executionof individual steps (e.g. discovery, individual CRUD operations), and sois unable to optimize them together. As such, the current mechanismsdescribed above result in overhead of either the amount of messagingrequired and/or the number of limited use, short-lived groups created.However, having the ability to request resource discovery at the sametime with desired CRUD operations may introduce significantoptimizations.

In addition, current mechanisms providing multiple filter criteria to bematched against the same resource rather than against multiple relatedresources, result in limitations in the usefulness of the results whichmay be obtained through any single discovery request.

Finally current processing of RESTful operation requests do not allowfor differentiation in exception/ condition handling at the Receiver404, which constrains their use by applications with differentiatedneeds.

Nomenclature

As discussed above, in many cases a resource discovery operation isfollowed by a batch of new CRUD requests targeting the resourcediscovering outcome. In a new solution, the batch of CRUD operations canbe coupled with the resource discovery operation and directly performedon the discovered resources, without initiating new/separate CRUDrequests.

The enhancements incorporate elements of filtering and discovery withthe traditional CRUD operations. The naming convention provided in thissection seeks to clarify the terms used in the following descriptions.

Filter Base: The resource used as starting point for a discoveryoperation, whose descendants are subject to filter criteria.

Matched Resource: A resource for which the filter criteria is true.

Filtering Result: The result of a filtering or discovery operation maybe composed of Matched Resources or resources related to the MatchedResources, depending on operation parameters. It may consist of one ormore resources.

Target Resource Set: One or more resources which are the target of aCRUD operation. The Target Resource Set may be the same as the FilteringResult of the discovery operation, or be composed of resources relatedto the Filtering Result, depending on operation parameters.

Operation Result: Indicates the result of the CRUD on the TargetResource Set. For the enhanced operations described here it may be theresult of the operation on multiple resources, if the Target ResourceSet consists of multiple resources. The format of the operation resultincluded in the result message may vary based on options provided in therequest: e.g. resources, resources and child resources etc.

Overview

The upcoming sections describe enhancements to RESTful operations.Overall enhancements to Request messages are described, including:

-   -   New request message parameters and new functionality at the        Originator 402 and Receiver 404 which differentiates the        resources for which criteria matching is applied from the        resources included in the discovery/ filtering results. Enhanced        functionality at the Originator 402 and Receiver 404 linking        RESTful and discovery operations.    -   Enhancements to Filter Criteria (e.g. to discover resources that        have a parent or a child that match certain filter criteria). It        also introduces enhanced Filter Directives (e.g. to request        creation of a group for the resources matching the filter        criteria, or to specify the relation between Target Resources        and Matched Resources)    -   Enhanced Exception Handling: for instance to change the behavior        when certain conditions or exception situations occur.

The procedural effects of the enhancements summarized above and providesfurther details for the parameter usage at both Originator 402 andReceiver 404.

oneM2M embodiments are described along with further details onprocessing, by being able to use concrete, standardized examples ofresources to the operations described

Request Message Enhancements New Request Message Parameters

This section illustrates the functional enhancements to the Requestmessages by introducing new operation parameters.

In general the flow that governs the information exchange procedures isbased on the use of Request and Response messages. Requests are sent byan Originator 402 to a Receiver 404 and contain parameters which may bemandatory or optional. Certain parameters may be mandatory or optionaldepending upon the requested operation.

We assume the existence of the following Request message parameters:

-   -   Operation: Specifies the exact RESTful operation to be executed,        e.g. CREATE, etc.    -   To: Address of the target resource where the operation is to be        executed    -   FilterCriteria: Criteria for condition matching    -   Content: Resource content to be used in the operation, e.g.        content of a resource to be created. Its presence is assumed not        to be mandatory for all operations.

We also assume the existence of the following Response messageparameters:

-   -   Response Code: Parameter indicating the success or failure of        the operation. It may include status information providing        further execution details    -   Content: Resource content based on the operation result, e.g.        content of a resource which has been created. Its presence is        assumed not to be mandatory for all operations.

The new operation parameters are described for a RESTful requestoperation.

(NEW) FilterBase: Address of the root where the discovery begins onHosting CSE,

Choices include, but are not limited to:

-   -   FilterCSEBase: Receiver 404 starts the discovery at the CSEBase;    -   (FilterAddress): Receiver 404 starts the discovery at the        specified address included in this field.    -   NULL or DEFAULT (or not present): No enhanced functionality is        requested and regular processing is performed.

If FilterBase is present and different than NULL or DEFAULT, it canindicate that the operation is treated as an enhanced operation.

Sometimes requests are routed through a transit CSE to a finaldestination which is the Receiver 404. For regular operations thetransit CSE routs messages to the Receiver 404 pointed by the Toaddress. For enhanced operations, indicated by the presence of theFilterBase address, the transit CSE will route messages to theFilterBase address. All other processing is the same as in the directcommunication cases presented in this paper.

The FilterCSEBase choice is resolved at the Receiver 404 into thecorresponding URI. Implementation may use only the second choice, wherethe actual address is provided, without losing any of the functionalitydescribed above

(NEW) CompositeResult: Indicates the expected components of the Contentfield in the Result message to the Originator 402 .

Choices based on the described functionality include, but are notlimited to:

-   -   FilteringResult: Receiver 404 will return the Filtering Result        of the discovery operation, based on the parameters specified by        the Originator 402 (see Filter Criteria below)    -   OperationResult: Receiver 404 will return the result of the        RESTful operation on the Target Resource Set    -   FilteringAndOperationResult: Receiver 404 will return both the        filtering Result and the result of the RESTful operation on the        Target Resource Set    -   Nothing or DEFAULT (or not present): Receiver 404 returns no        result

(NEW) ExceptionHandling: Indicates handling of certain conditions orexceptions.

Choices include, but are not limited to:

-   -   UpdateExistingName. Used when the Receiver 404 creates a        resource. If the Originator 402 requests “UpdateExistingName”,        the Receiver 404 is required to use the name supplied by the        Originator 402. As a result, certain operation actions will need        to be modified (for instance CREATE)    -   NULL or DEFAULT (or not present) Receiver 404 uses default        exception handling

The functionality of an existing RESTful request parameter can beenhanced as follows

(ENHANCED) To: Address, currently required to resolve to a unique URIaddressing the target resource where the CRUD operation is to beexecuted.

In this proposal, we add the option of using the To parameter to providea relative relationship between the resources discovered (FilteringResults) and the resources on which the RESTful operation is to beperformed (Target Resources).

This option is valid for enhanced operations only and for this purposethe To field must be provided as a relative path, which is to beconcatenated with the Filtering Result to obtain the Target ResourceSet. If the address provided in the To field is NOT relative, the TargetResource Set is the same as the Filtering Result.

Other possible enhancements to the Filter Criteria are detailed in theEmbodiments section.

Enhancements for Filtering Criteria and Directives

We assume the possibility of providing Filter Criteria in exitingRESTful operations, to be used for filtering or discovery purposes. Inorder to enrich the existing filtering and discovery processes, wepropose the introduction of several new parameters to indicate filteringcriteria which are to be used to match related resources, e.g. to matchattributes of a child or parent resources.

Here, the following new search parameters are described:

-   -   (NEW) childResourceType: The Matched Resource has to have a        child resource of this type    -   (NEW) childResourceName: The Matched Resource has to have a        child resource with this name    -   (NEW) childLabels: The Matched Resource has to have a child        resource with a label matching the given value    -   (NEW) childAttribute: The Matched Resource has to have a child        resource with an attribute matching the given value    -   (NEW) parentResourceType: The Matched Resource has to have a        resource of this type as its parent    -   (NEW) parentResourceName: The Matched Resource has to have a        resource of this name as its parent    -   (NEW) parentLabels: The Matched Resource has to have a resource        with a label matching the given value as its parent    -   (NEW) parentAttribute: The Matched Resource has to have a        resource with an attribute matching the given value as its        parent

Parameters indicating how the Filter Criteria should be used, thereforeacting as Filtering Directives can also be used.

(NEW) returnRelativeRelationship informs the Receiver 404 how the resultof the discovery (Filtering Result) are related with the resources forwhich the discovery criteria applies (Matched Resource Set), with thefollowing relationship options:

-   -   Self: the discovered resources are the same as the matched        resources;    -   Parent: the discovered resources are the parents of the matched        resources. The Receiver 404 may implement logic to remove        duplicate parent resources from the Filtering Result.    -   Semantics: the discovered resources are sub-resources containing        semantic information for each matched resources, e.g. in oneM2M        the <semanticDescriptor> sub-resource will be returned in the        Filtering Result    -   Subscription: the discovered resources are sub-resources        containing subscription information for each matched resources,        e.g. in oneM2M the <subscription> sub-resource will be returned        in the Filtering Result    -   Latest: the discovered resources are the latest instances of        each matched resource. This applies when the criteria given        targets resources which retain multiple instantiations, e.g. in        oneM2M <container> resources    -   Oldest: the discovered resources are the oldest instances of        each matched resource. This option is valid when the criteria        applies to resources which retain multiple instantiations, e.g.        in oneM2M <container>resources

For all returnRelativeRelationship values, if a resource is matched butno resource with the given relative relationship is found, the result istreated as if no match was found.

An example based on oneM2M: The <AE1> resource is matched based on thegiven criteria and returnRelativeRelationship==Subscription, but <AE1>has no <subscription> sub-resources. The case is treated as if <AE1> didnot match the given the criteria in the first place, so it is removedfrom the Matched Resource Set.

(NEW) formGroup: Form a group based on the results of the filteringprocess. Choices include, but not limited to: MatchedResources,FilteredResources, OperationResult.

(NEW) grouplD: If formGroup is present, a grouplD might be indicated bythe Originator 402. If formGroup is not present this parameter isignored.

Exception Handling Indications

Each operation has default exception handling, however, the Originator402 may specify enhanced exceptional or conditional handling. Forinstance consider an oneM2M case where a specific <AE> resource (sayAE1) already has a child <subscriptionX> resource, i.e. a child resourceof type <subscription> named “subscriptionX”. In such a case, when anOriginator 402 tries to CREATE a new <subscription> resource named“subscriptionX”, the current behavior of the Receiver 404 may be tocreate another child resource, e.g. <subscriptionAlt> by changing thename provided by the Originator 402 , and to return the new name withthe operation result.

We propose that the Originator 402 may request the subscription creationwith ExceptionHandling=UpdateExistingName. In such a case, the Receiver404 is forced to interpret the operation as an UPDATE to the existing<subscriptionX> child resource, and not to create another one. TheReceiver 404 will first verify create rights of the Originator 402 atthe addressed resource <AE1> AND update rights of the Originator 402 atthe resource to be updated <AE1/subscriptionX>. If these rights allowthe operation, it will execute an UPDATE of <AE1/subscriptionX> with theprovided content.

The possible choices for ExceptionHandling may be expanded based onimplementation needs. For example, another value “IgnoreExistingName”may be used to request the Receiver 404 to ignore the existence of achild resource with the given name. Therefore, the Receiver 404 shalldelete the old resource and replace it with the content of the newCreate operation.

Alternatives

The enhancements presented above may have alternative implementations.

Modifications of existing parameters: to reflect the new functionality,instead of introducing the new parameter FilterBase, the use of the Toparameter may be modified further. A simple bit flag (e.g. Eflag) may beused to indicate an enhanced operation and the To field reused toprovide the FilterBase address for this case. Since no relative pathcould be provided in this case, the Target Resource Set may beconsidered by default to be the same as the Filtered Result for allenhanced operations using such an implementation. Alternatively, afiltering directive similar to returnRelativeRelationship may be used.For example a tar getRelativeRelationship filter directive may beintroduced with similar choices of values (e.g. Self, Parent, Semantics,etc.)

New Operation types: to reflect the new functionality, new RESTfuloperation types may be created, e.g. DiscCreate (Discovery & Create),DiscUpdate (Discovery & Update), DiscDelete (Discovery & Delete).Similarly, assuming that regular Discovery is implemented using aRetrieve operation, a separate EnhDisc (Enhanced Discovery) operationmight be created to reflect an ENHANCED discovery operation, separatefrom Retrieve or Retrieve with regular discovery/filteringfunctionality.

The new operation types can be implemented as additional choices to theC, R, U, D values for the Operation parameter of the Request message,e.g. DiscC, DiscU, DiscD, and EnhDisc may be added to the list of validoperation values. Assuming the above new operation types, the FilterBaseparameter may no longer be needed as indicator for the enhancedfunctionality. As such the FilterBase and To parameters may be collapsedinto one parameter (e.g. To) whose significance is conditional based onthe operation type, as described in the previous sections.

For the new operations new access control policies may be defined, orthe Receiver functionality is specified to use the access rights of theindividual operations, as detailed in the following sections.

Operation Procedures

FIG. 9 illustrates a call flow for generic enhanced operations of onesolution and details the Receiver 404 processing based on the newparameters. FIG. 10 illustrates an example call flow using enhancedCREATE operation for the TaskManager use case that will be described indetail. FIG. 10 illustrates one example of the generic call flow of FIG.9.

The following subsections provide additional details using the oneM2Muse case, where the TaskManager application subscribes to theStatusContainer of registered AEs only if they meet given sector and themaintenance state criteria.

In the example of FIG. 10, the Originator 402 issues a CREATE (C)request towards a Receiver 404, but the operation needs to be performedon resources to be discovered first by the Receiver 404 by evaluatinggiven criteria.

Corresponding processing also applies to the other CRUD operations.

Similarly, the processing can be generalized to include other validvalues and combinations of parameters. Further illustrations are alsoprovided below.

In step 0 of FIG. 10, as a pre-requisite, the Originator 402 knows therelative address of the resource where the operation is to be performed.This may have been obtained by a prior discovery procedure orpre-configuration. For example the TaskManager AE_tm 604 performeddiscovery procedures at MN-CSE1 602 in prior searches and thereforeunderstands its tree structure, particularly the resources created whenthe equipment AEs register with MN-CSE1 602, including those storingoperation status information (in this case the child <statusContainer>of the <AE> resources). MN-CSE1 602 has the generic role of Receiver 404of the Request messages, as well as Hosting CSE in procedures using moregeneralized terms.

In step 1 of FIG. 10, the Originator 402 issues a CREATE requestincluding the following parameters:

-   -   (NEW) FilterBase=FilterCSEBase    -   Reflects the fact that the whole CSEBase tree will be searched        for our use case.    -   FilterCriteria: (label=sector#42 AND label=maintenanceNotCurrent        AND returnRelativeRelationship=self).    -   Reflects the resource matching criteria for our use case    -   Content: representation of the <subscription> sub resource to be        created as child of all the target resources    -   (NEW) CompositeResult=OperationResult    -   For our use case it indicates what the expected components of        the result are all the created resources    -   (NEW) ExceptionHandling=NULL    -   For our use case no special handling is necessary    -   (MODIFIED) To=. . . /StatusContainer For our use case enhanced        operation processing is indicated by the existence of        FilterBase, so the To field may be relative path. The Receiver        404 is instructed to concatenate . . . /StatusContainer with the        addresses of the resources in the Filtering Result in order to        determine the addresses of the resources in the Target resource        Set.

The Receiver 404 processing is based on the type of the requestreceived, as well as the contents of all parameters provided by theOriginator 402 in the request, including the Filtering Criteria

In step 2 of FIG. 10, the Receiver 404 receives the operation requestand checks the parameters. Sub steps 2 a-2 g are described below.

In step 2 a of FIG. 10, the Receiver 404 finds the search (i.e.discovery) base address based on FilterBase. In our use case it is/CSEBase. If FilterBase is not present then this is not an enhancedoperation, so it proceeds from step D verifying the existence of theoperation target.

In step 2 b of FIG. 10, the Receiver 404 searches starting from theFilter Base/CSEBase for resources meeting the conditions (FilterCriteria). In each iteration it finds a resource /AEk, where k is anindex of found AE resources matching the filter criteria, and it isincremented with each iteration i. For simplicity, these found resourcesare denoted as AEk (k incremented for kth matching resource) in theremainder of the document. Each AEk resource is a Matched Resource.

In step 2 c of FIG. 10, based on returnRelativeRelationship=self eachMatched Resource becomes candidate to be added to the Filtering Result.The Receiver 404 adds this candidate to the Filtering Result afterchecking the discovery rights of the Originator 402 at AEk. If thediscovery operation is not allowed by the ACP a corresponding error codeis generated.

Note that in the current RETRIEVE based discovery, the full treerepresentation of the search result is created for the operation result.In the processing described here, the Filtering Result may be insteadonly a list of resources meeting the conditions, without full treerepresentation

In step 2 d of FIG. 10, based on To: . . . /StatusContainer, theReceiver 404 verifies that each path /AEk/StatusContainer is valid, i.e.it corresponds to a child resource of the Filtering Result. If not itdiscards AEk from the filtering result and generates a correspondingerror code.

In step 2 e of FIG. 10, based on ACP and the originator 402 CREATErights at /AEk/StatusContainer the Receiver 404 performs the CREATEoperation on /AEk/StatusContainer of a <subscription> resource. If thecreate operation is not allowed a corresponding error code is generated.

In step 2 f of FIG. 10, the Receiver 404 may assign values for someattributes of the created resource, as mandated by the operationrequirements. For example the operation may require it to assign aresource ID for the newly created resource, or to assign values tocertain attributes such as ParentlD, creation time, etc.

In step 2 g of FIG. 10, the Receiver 404 generates a composite responsecode based on the individual error codes in the previous steps. TheReceiver 404 also assembles the content of the response based onCompositeResult. In this case CompositeResult=OperationResult, so thecontent field will contain the created <subscription> resources. Whenthe tree search is exhausted it generates the response to be sent to theOriginator 402.

If the formGroup indicator (and possibly grouplD) is included in therequest, the processing at the Receiver 404 includes the following: TheReceiver 404 forms a resource group with the given grouplD (or aself-selected ID) and in each search iteration would add new members.The members to be added depend on the value provided in formGroup (e.g.MatchedResources, ReturnedResources, OperationResult). As such, thisprocessing may be incorporated in steps B, C or E, i.e. whenever a newvalid resource is found for the Matched Resource Set or FilteringResult, or after an operation result is determined.

In step 3 of FIG. 10, the Originator 402 receives the response messageand processes the mandatory and optional parameters contained, includingthe Composite Response Code. Based on the request parameters additionalinformation might be included, such as a list of all the newly createdresources, which may be used for further processing at the Originator402.

It is understood that the entities performing the steps illustrated inFIGS. 9-10 are logical entities that may be implemented in the form ofsoftware (i.e., computer-executable instructions) stored in a memory of,and executing on a processor of, a network node or computer system suchas those illustrated in FIG. 14C or FIG. 14D. That is, the method(s)illustrated in FIGS. 9-10 may be implemented in the form of software(i.e., computer-executable instructions) stored in a memory of a networknode, such as the node or computer system illustrated in FIG. 14C orFIG. 14D, which computer executable instructions, when executed by aprocessor of the node, perform the steps illustrated in FIGS. 9-10. Itis also understood that any transmitting and receiving steps illustratedin FIGS. 9-10 may be performed by communication circuitry of the nodeunder control of the processor of the node and the computer-executableinstructions (e.g., software) that it executes.

oneM2M Embodiment

The following sections show how the new parameters described above maybe applied in oneM2M embodiments. In later sections, we describespecific examples of messages with details of the resultingfunctionality, processing and results.

This section describes a solution for an oneM2M embodiment of theenhancements.

Table 4 depicts the oneM2M request parameter list detailed earlier,together with the newly introduced parameter (FilterBase, CompositeResult, and ExceptionHandling) and possible changes in usage of theother parameters.

Table 5 depicts the corresponding oneM2M FilterCriteria list togetherwith newly introduced parameters for the FilterCriteria.

Both tables highlight also possible modifications and clarifications tobe brought to the usage of the existing parameters.

For the solutions described below the presence of the FilterBaseparameter is the indicator of enhanced functionality. The discoveryfunctionality described in oneM2M-TS-0001, oneM2M FunctionalArchitecture V2.1.0 and uses another parameter, namely filter Usage, asindicator that a RETRIEVE operation should be used for discovery.FilterBase existence may be a better indicator for using FilterCriteriafor the existing, RETRIEVE-based discovery operation as well. Howevereither method would work for this purpose.

TABLE 4 Request Parameter List Request Parameter Criticality Description(ENHANCED) To Mandatory Address of the target resource or targetattribute for the operation. When FilterBase present this is a relativepath, this path will be concatenated with the addresses of the resourcesin the Filtering Results in order to determine the addresses of theresources in the Target. Resource Set for the RESTful operation.Otherwise this is an absolute path. From Mandatory Identifierrepresenting the Originator Operation Mandatory Operation to beexecuted: Create (C), Retrieve (R), Update (U), Delete (D), Notify (N).Request Identifier Mandatory ID enabling tracking of Requests andcorresponding Responses. Content Conditional (C) content of the newresource to be created based on (U) content to be replaced in anexisting resource Operation: (N) notification information MandatoryOptional for: for C, U, N, (R) list of attributes to be retrievedOptional for R Resource Type Conditional, Resource type for the resourceto be created. Mandatory for C Role Optional Originator role to be usedin role based access control Originating Optional Originating timestampof when the message was Timestamp built. Request Expiration OptionalIndicates when the request messages (including Timestamp delay-tolerant)should expire Response Expiration Optional Indicates when the responsemessages (including Timestamp delay-tolerant) should expire ResponseType Optional Indicates what type of response shall be used. Optionsare: nonBlockingRequestSynch, nonBlockingRequestAsynch, blockingRequestResult Content Optional Indicates what the expected components of theresult are. Options are: attributes, hierarchical- address,hierarchical-address + attributes, attributes + child-resources,child-resources, attributes + child-resource-references, child-resource-references, nothing, original-resource (NEW) Note: The newlyintroduced Composite Result parameter might be implementedindependently, or merged with Result Content, in which case somemodifications of its use might be specified. Result Persistence OptionalIndicates the duration for which the address containing the responses isto persist. Operation Execution Optional Indicates the time when thespecified operation Time is to be executed by the target CSE EventCategory Optional Indicates the event category that should be used tohandle this request in transit, such as immediate, bestEffort, latestDelivery Aggregation Optional Enables aggregation of one or more requestfor delivery to the same CSE(s), depending on policies Group RequestOptional Identifier optionally added to group requests that Identifieris to be fanned out, in order to detect loops and avoid duplicatedoperations. Filter Criteria Optional Conditions for filtered retrieveoperation are described in the next section. It is used for resourcediscovery and general retrieve, update, delete requests. (NEW) Note:filterUsage may no longer be needed to indicate a discovery procedureDiscovery Result Type Optional Indicates the preference of theOriginator for the format of returned information in the result of theoperation. Options are: Hierarchical addressing, non-hierarchicaladdressing (NEW)FilterBase Optional Address of the root where thediscovery begins on Hosting CSE, Choices: FilterCSEBase, Exact URI to beused as filtering base. If not present, the processing follows currentspecifications for regular operations, where some filtering is supportedfor some of the operations. (NEW)Composite Optional Indicates what theexpected components of the Result result are. Choices based on newfunctionality: FilteringResult, OperationResult, Nothing Note: Thisparameter might be implemented independently, or merged with ResultContent above, insuring that all necessary choices are available. (NEW)Optional Indicates handling of certain exceptions. ExceptionHandling:Choices: UpdateExistingName, IgnoreExistingName. If not present, thedefault exception handling occurs (see oneM2M-TS- 0001, oneM2MFunctional Architecture V2.1.0)

TABLE 5 oneM2M FilterCriteria List Search Parameter Criterion met ifcreatedBefore The Matched Resource was created before createdBeforecreatedAfter The Matched Resource was created after createdBeforemodifiedSince The Matched Resource has been modified since modifiedSinceunmodifiedSince The Matched Resource has not been modified sinceunmodifiedSince stateTagSmaller The Matched Resource has stateTagattribute smaller than stateTagSmaller stateTagBigger The MatchedResource has stateTag attribute larger than stateTagBigger expireBeforeThe Matched Resource has expirationTime attribute before expireBeforeexpireAfter The Matched Resource has expirationTime attribute afterexpireAfter labels The Matched Resource has labels attribute matchinglabels search parameter. The labels are tokens used as keys fordiscovery purposes resource Type The Matched Resource is of typeresourceType sizeAbove The Matched Resource is a <contentInstance>resource and its contentSize attribute is equal to or greater than thesizeAbove value sizeBelow The Matched Resource is a <contentInstance>resource and its contentSize attribute is smaller than the sizeBelowvalue contentType The Matched Resource is a <contentInstance> resourceand its contentInfo attribute matches the contentType value attributeThe Matched Resource has the corresponding matching resource attribute(NEW) The Matched Resource has to have a child resource of thischildResourceType type (NEW) The Matched Resource has to have a childresource with this childResourceName name (NEW) childLabels The MatchedResource has to have a child resource with a label matching the givenvalue (NEW) childAttribute The Matched Resource has to have a childresource with an attribute matching the given value (NEW) The MatchedResource has to have a resource of this type as parentResourceType itsparent (NEW) The Matched Resource has to have a resource with this nameparentResourceName as its parent (NEW) parentLabels The Matched Resourcehas to have a resource with a label matching the given value as itsparent (NEW) parentAttribute The Matched Resource has to have a resourcewith an attribute matching the given value as its parent Filter criteria(others) Role: limit This parameter is not used as search criterion,rather as in formatting/limiting the way the search result is returnedfilterUsage This parameter is not used as search criterion, rather forindicating the use of the filter criteria for discovery purposes NOTE:this parameter might not be used to indicate a discovery procedure, ifthat indication is provided by the existence of filterBase (NEW) Theresources composing the Filtering Result may have thereturnRelativeRelationship following relationship with the MatchesResource: Self, Parent, Semantics, Subscription, Latest, Oldest (NEW)formGroup Form a group based on filterCriteria Options:MatchedResources, ReturnedResources, OperationResult. (NEW) groupID IfformGroup is present, a groupID might be indicated by the Originator. IfformGroup is not present this parameter is ignored

This section uses the oneM2M embodiment and parameter descriptionsprovided in the previous section and provides usage examples based ondifferent configurations. Not all possible permutations have beenexemplified.

In these following examples, as a pre-requisite, the Originator 402knows the relative path to be used in the To parameter, generally basedon a prior discovery procedure. This corresponds with the use of theseenhanced operations in numerous use cases in which the Originator 402has performed certain discovery and CRUD operations many times, so thereis prior knowledge of the resource tree structure.

In this case, the filtering request fulfills the role of a search basedon information contained in the resources, rather than to discover theresource tree structure. The Enhanced RESTful operations are not meantto replace the existing CRUD operations or resource tree structurediscovery function, but to complement them.

FIG. 11 depicts a generic Request and Response flow. The parametervalues specific to each case are detailed in the respective sections.

Example 1: Create sub resource to all resources found to meet attributeconditions at two hierarchical levels

Functionality: Creates a subscription to all newer containers (thosecreated after time “myDate”) which are children of AEs with attributeappName==myApp

In many cases device applications (AEs) residing on different devicesregister using the same the appName attribute. A user interested in aspecific service from all devices registered to the same CSE cansubscribe to all the newer containers created by these services, withthe discovery and the subscription creation being performed together.

In step 1 of FIG. 11 for Example 1, a request is sent using the requestformat:

To: CSEBase

Operation: CREATE (C)

FilterBase: FilterCSEBase

-   -   Filter Criteria:    -   resourceType==<container>, createdAfter==myDate,        parentResourceType==<AE>, parentAttribute appName==myApp        returnRelativeRelationship==Self

Content: <subscription>

ResultContent: hierarchical-address+attributes

CompositeResult: OperationResult

-   -   ExceptionHandling: NULL

In step 2 of FIG. 11 for Example 1, processing is done with sub-steps 2a-2 g.

In step 2 a of FIG. 11 for Example 1, the Hosting CSE finds the searchbase FilterBase i.e. CSEBase

In step 2 b of FIG. 11 for Example 1, the Hosting CSE searches startingfrom the search base CSEBase for all resources meeting the conditions(resourceType==<container>, createdAfter==myDate,parentResourceType==<AE>, parentAttribute appName=myApp). It findsCSEBase/AEk/containerX as a Matched Resource.

In step 2 c of FIG. 11 for Example 1, based onreturnRelativeRelationship==Self, the same resource is a candidate to beadded to the Filtering Result, depending on ACP and Originator 402discovery rights. We assume that the Originator 402 has discovery rightsfor CSEBase/AEk/containerX

In step 2 d of FIG. 11 for Example 1, based on the To address not beinga relative path, the Target Resource Set is the same as the FilteringResult. The Hosting CSE verifies that the path CSEBase/AEk/containerX isvalid for each resource in the Target Resource Set.

In step 2 e of FIG. 11 for Example 1, based on ACP and the Originator402 CREATE rights at CSEBase/AEk/containerX the Hosting CSE performs theCREATE operation of a <subscription> resource. We assume the Originator402 has create rights. Based on ExceptionHandling: NULL no specialhandling of the RESTful operation is needed.

In step 2 f of FIG. 11 for Example 1, the Hosting CSE may assign valuesfor some attributes of the created resource, as mandated by the regularoperation requirements

In step 2 g of FIG. 11 for Example 1, the Hosting CSE generates theComposite Response Code and the response content. Based onCompositeResult i.e. OperationResult and ResultContent:hierarchical-address+attributes the result content will contain theaddresses of all the subscription resources created, i.e.SEBase/AEk/containerX/subscription and their attributes

Example 2: Create sub resource to a specific child of each matchedresource, matches based on filters at two hierarchically relative levels(parent and child)

Functionality: Given an application AE1 that forms a container fortemperature readings from many platforms/sensors, so there may beseveral nested as well as parallel containers included. Find all themeasurement storing containers who have ZigBee temperature information,as described by the container's ontologyRef pointing to the ZigBeetemperature sensor ontology. Then create a subscription to the semanticdescription resource of the filtering result to monitor semanticdescription changes. Returns the hierarchical addresses of thesubscription resources created.

In step 1 of FIG. 11 for Example 2, a request is sent using the requestformat:

To: CSEBase

Operation: CREATE (C)

FilterBase: ICSEBase/AE1

Filter Criteria:

-   -   parentType <container>, resourceType <container>, attribute        ontologyRef==http://[ZigBeeOntology]#TemperatureSensor        returnRelativeRelationship ==Semantics

Content: <subscription>

ResultContent: hierarchical-address

CompositeResult: OperationResult

ExceptionHandling: NULL

In step 2 of FIG. 11 for Example 2, processing sub-steps 2 a-2 g aredone.

In step 2 a of FIG. 11 for Example 2, the Hosting CSE finds the searchbase i.e. FilterBase=/CSEBase/AE1

In step 2 b of FIG. 11 for Example 2, the Hosting CSE searches startingfrom the search base /CSEBase/AE1 for all resources meeting theconditions (parentType <container>, resourceType <container>, attributeontologyRef==http://[ZigBeeOntology]#TemperatureSensor) and will findall matching containers i.e. finds all . . . /containerK matching(whichmay be at various levels in the tree based at /CSEBase/AE1)

In step 2 c of FIG. 11 for Example 2, based onreturnRelativeRelationship==Semantics, the . . ./containerK/semanticDescriptor resource is a candidate to be added tothe Filtering Result, depending on ACP and the Originator 402 discoveryrights. We assume that the Originator 402 has discovery rights

In step 2 d of FIG. 11 for Example 2, based on the To address not beinga relative path, the Target Resource Set is the same as the FilteringResult. The Hosting CSE verifies that the path to . . ./containerK/semanticDescriptor is valid for each result in the TargetResource Set.

In step 2 e of FIG. 11 for Example 2, based on ACP and the Originator402 CREATE rights at . . . /containerK/semanticDescriptor the HostingCSE performs the CREATE operation of a <subscription>resource. We assumethe Originator 402 has create rights.

In step 2 f of FIG. 11 for Example 2, the Hosting CSE may assign valuesfor some attributes of the created resource, as mandated by the regularoperation requirements

In step 2 g of FIG. 11 for Example 2, the Hosting CSE generates theComposite Response Code and the response content. Based onCompositeResult i.e. OperationResult and ResultContent:hierarchical-address the result content will contain the addresses ofall the subscription resources created, i.e./containerK/semanticDescriptor/subscription without the attributes

Example 3: Updates an attribute for all resources with a given relationto the resources in the Filtering Result

Functionality: Finds all the devices (AEs) with location containersupdated recently (that is since time “myTime”), then updates a label onthe tempMeasurement container known to be present in all these AEs forfuture filtering of only those tempMeasurement resources. Thisfunctionality effectively discovers the devices with newly updatedlocations, and at the same time it labels the measurement containers tobe easily discoverable for easy future identification.

In step 1 of FIG. 11 for Example 3, a request is sent using the requestformat:

To: . . . /tempMeasurement

Operation: UPDATE (U)

FilterBase: FilterCSEBase

Filter Criteria:

-   -   parentResourceType==<AE>, resourceType==<container>,        resourceName==locationContainer, modifiedSince==myTime        returnRelativeRelationship==Parent

Content: labels=tempSensorMoved

ResultContent: nothing

CompositeResult: OperationResult

ExceptionHandling: NULL

In step 2 of FIG. 11 for Example 3, processing sub-steps 2 a-2 g aredone.

In step 2 a of FIG. 11 for Example 3, the Hosting CSE finds the searchbase FilterBase =CSEBase

In step 2 b of FIG. 11 for Example 3, the Hosting CSE searches startingfrom the search base CSEBase for all resources meeting the conditions(parentResourceType==<AE>, resourceType==<container>, resourceNamelocationContainer, modifiedSince==myTime).

It will find the corresponding locationContainercontainers as MatchedResources: CSEBase/AEk/locationContainer.

Based on returnRelativeRelationship==Parent each CSEBase/AEk becomes acandidate for Filtering Result

In step 2 c of FIG. 11 for Example 3, for each iteration, depending onACP and the Originator 402 discovery rights at CSEBase/AEk the HostingCSE adds this resource to the Filtering Result. We assume that theOriginator 402 has discovery rights.

In step 2 d of FIG. 11 for Example 3, based on To=. . ./tempMeasurement, the Hosting CSE forms the Target Resource Set for theUPDATE operation, so the set will be composed of allCSEBase/AEk/tempMeasurement resources

The Hosting CSE verifies that the path CSEBase/AEk/tempMeasurement isvalid for each resource in the Target Resource Set.

In step 2 e of FIG. 11 for Example 3, based on ACP and the Originator402 UPDATE rights at Base/AEk/locationContainer the Hosting CSE performsthe UPDATE operation of the CSEBase/AEk/tempMeasurement resource byupdating the labels attribute (i.e. adding″ tempSensorMoved″). We assumethe Originator 402 has update rights.

In step 2 f of FIG. 11 for Example 3, the Hosting CSE may assign valuesfor some attributes of the updated resource, as mandated by the regularoperation requirements

In step 2 g of FIG. 11 for Example 3, the Hosting CSE generates theComposite Response Code and the response content. Based onCompositeResult i.e. OperationResult and ResultContent i.e. Nothing nocontent is sent back with the response

Example 4: Deletes a resource instance relative to the matches found tomeet conditions at three hierarchical levels

Functionality: Finds all the AEs with <container> resources to which aspecific destination has subscriptions, then deletes the latest<contentlnstance> of the tempMeasurement container.

This may be a case where a subscriber to notifications may be aware thata certain condition occurs (e.g. the latest measurement is known to beinvalid) and uses one operation to discover all relevant resources toand delete the latest results.

In step 1 of FIG. 11 for Example 4, a request is sent using the requestformat:

To: CSEBase

Operation: DELETE (D)

FilterBase: FilterCSEBase

Filter Criteria:

-   -   resourceType==<container>, resourceName==tempMeasurement,        childResourceType <subscription>, childAttribute        notificationURI==myURI        parentResourceType==<AE>returnRelativeRelationship ==Latest

Content: N/A

ResultContent: N/A

CompositeResult: Nothing

ExceptionHandling: NULL

In step 2 of FIG. 11 for Example 4, processing sub-steps 2 a-2 g aredone.

In step 2 a of FIG. 11 for Example 4, the Hosting CSE finds the searchbase i.e. FilterBase=CSEBase.

In step 2 b of FIG. 11 for Example 4, The Hosting CSE searches startingfrom the search base CSEBase for all resources meeting the conditions(resourceType==<container>, resourceName==tempMeasurement,childResourceType <subscription>, childAttribute notificationURI==myURI,parentResourceType==<AE>) so it will find all containers with thecorresponding attribute in the Subscription, i.e. finds allCSEBase/AEk/tempMeasurement as Matched Resources. Based onreturnRelativeRelationship==Latest, the latest <contentlnstance> of eachCSEBase/AEk/tempMeasurement is a candidate to the Filtering Result

In step 2 c of FIG. 11 for Example 4, for each iteration, depending onACP and Originator 402 discovery rights atCSEBase/AEk/tempMeasurement/latest, the Hosting CSE adds this resourceto the Filtering Result. We assume that the Originator 402 has discoveryrights.

In step 2 d of FIG. 11 for Example 4, based on To==CSEBase the HostingCSE sets the Target Resource Set for the DELETE operation to be the sameas the Filtering Result. The Hosting CSE also verifies that the pathCSEBase/AEk/tempMeasurement/latest is valid for each resource in theTarget Resource Set.

In step 2 e of FIG. 11 for Example 4, based on ACP and Originator 402DELETE rights at CSEBase/AEk/tempMeasurement/latest the Hosting CSEperforms the DELETE operation of the latest <contentlnstance>resource.We assume the Originator 402 has delete rights.

In step 2 f of FIG. 11 for Example 4, the Hosting CSE generates theComposite Response Code. Based on CompositeResult==Nothing, no contentneeds to be included in the response. When the tree search is exhaustedit generates the response to the Originator 402

In oneM2M oneM2M-TS-0001, oneM2M Functional Architecture V2.1.0 anoperation targeting virtual resource <container>/latest is applied tothe latest instantiation of the <contentlnstance> child of the<container> resource. Therefore in this example, an operation onCSEBase/AEk/tempMeasurement/latest is executed on a <contentlnstance>resource

Example 5: Uses exceptionHandling to selectively create or updateresources relative to the resources in the Filtering Result and createsa group for future use

Functionality: Finds all the devices (AEs) with location containersupdated recently (that is since time “myTime”), then creates or updatesthe subscription to a specific container. A group of the matchedresources is formed for possible future use.

This functionality may be used to discover the devices with newlyupdated locations and update subscriptions with a new notificationtarget, or create new subscriptions. At the same time it forms a groupof the locationContainer sub resources for future use, e.g. to requestfuture location updates to all as a group.

In step 1 of FIG. 11 for Example 5, a request is sent using the requestformat:

-   -   To: . . . /tempMeasurement    -   Operation: CREATE (C)    -   FilterBase: FilterCSEBase    -   Filter Criteria: parentResourceType==<AE>,        resourceType==<container>, resourceName ==locationContainer,        modifiedSince ==myTime returnRelativeRelationship ==Parent        formGroup ==MatchedResources grouplD: 35    -   Content: <my Subcription>    -   ResultContent: nothing    -   CompositeResult: OperationResult    -   ExceptionHandling: UpdateExistingName    -   Note: The current oneM2M CREATE procedure specifies in        oneM2M-TS-0001, oneM2M Functional Architecture V2.1.0 section        10.1.1.1 for processing at the receiver 404:    -   “Verify that the name for the created resource as suggested as        the resourceName attribute in Content parameter, if provided by        the Originator 402 in the CREATE Request message, does not        already exist among child resources of the target resource. If        no child within the targeted resource exists with the same        resourceName as suggested by the Originator 402, use that name        for the resource to be created. If a child uses the resourceName        already, the Receiver 404 assign a new name which shall be        returned to the Originator 402. If the name was not suggested by        the Originator 402, assign a name generated by the Receiver 404        to the resource to be created.” By using the ExceptionHandling:        UpdateExistingName the Receiver 404 can be instructed to modify        this default behavior as follows: If ExceptionHandling indicates        UpdateExistingName and a child uses the resourceName already,        the Receiver 404 does not generate a new name and does not        create a new resource. Instead, the Receiver 404 proceeds with        executing an Update operation on the existing child resource,        using the given Content. If ExceptionHandling is NULL or empty        the default processing occurs.

In step 2 of FIG. 11 for Example 5, processing sub-steps 2 a-2 g aredone.

In step 2 a of FIG. 11 for Example 5, the Hosting CSE finds the searchbase FilterBase =CSEBase

In step 2 b of FIG. 11 for Example 5, the Hosting CSE searches startingfrom the search base CSEBase for all resources meeting the conditions(parentResourceType==<AE>, resourceType==<container>, resourceNamelocationContainer, modifiedSince==myTime).

It will find the corresponding locationContainer containers as MatchedResources: CSEBase/AEk/locationContainer.

Based on formGroup==MatchedResources and groupID: 35 the Hosting CSEforms a group with grouplD 35 and adds eachCSEBase/AEk/locationContainer Matched Resource to the group as it isfound.

Based on returnRelativeRelationshi p==Parent each CSEBase/AEk becomes acandidate for Filtering Result

In step 2 c of FIG. 11 for Example 5, for each iteration, based on ACPand the Originator 402 CREATE rights at CSEBase/AEk the Hosting CSE addsthis resource to the Filtering Result. We assume that the Originator 402has discovery rights.

In step 2 d of FIG. 11 for Example 5, based on To==. . ./tempMeasurement the Hosting CSE knows that the CREATE operation needsto be performed on CSEBase/AEk/tempMeasurement

The Hosting CSE verifies that the path CSEBase/AEk/tempMeasurement isvalid for each resource in the Target Resource Set

In step 2 e of FIG. 11 for Example 5, based on ACP and the Originator402 create rights at CSEBase/AEk/tempMeasurement the Hosting CSEperforms the CREATE operation of the <mySubcription>resource. We assumethe Originator 402 has update rights.

Based on ExceptionHandling: UpdateExistingName, if a subscriptionresource named <mySubscription> exists, the Hosting CSE updates theexisting <mySubscription> resource.

In step 2 f of FIG. 11 for Example 5, the Hosting CSE may assign valuesfor some attributes of the updated resource, as mandated by the regularoperation requirements

In step 2 g of FIG. 11 for Example 5, the Hosting CSE generates theComposite Response Code and the response content. Based onCompositeResult i.e. OperationResult and ResultContent i.e. Nothing nocontent is sent back with the response

FIG. 12A-B illustrates an exemplary request processing flow chart.

It is understood that the entities performing the steps illustrated inFIGS. 11-12 are logical entities that may be implemented in the form ofsoftware (i.e., computer-executable instructions) stored in a memory of,and executing on a processor of, a network node or computer system suchas those illustrated in FIG. 14C or FIG. 14D. That is, the method(s)illustrated in FIGS. 11-12 may be implemented in the form of software(i.e., computer-executable instructions) stored in a memory of a networknode, such as the node or computer system illustrated in FIG. 14C orFIG. 14D, which computer executable instructions, when executed by aprocessor of the node, perform the steps illustrated in FIGS. 11-12. Itis also understood that any transmitting and receiving steps illustratedin FIGS. 11-12 may be performed by communication circuitry of the nodeunder control of the processor of the node and the computer-executableinstructions (e.g., software) that it executes.

Alternatives to the oneM2M Embodiment.

This section describes an alternate solution to the one described above.First we present alternatives to the request parameters, followed bysome to the filter criteria.

In this section some of the new attributes described above areimplemented using several different fields/parameters, while using thesame oneM2M request format as starting point. While the implementationis different, the addressed problem and use case are the same.

Multiple, Logically Nested Filter Criteria

New parameters for this solution are highlighted in Table 6, along withpossible modifications and clarifications to be brought to the usage ofthe existing parameters. In this example, we show an example for use of3 different filter criteria parameters in the request, two or more wouldwork similarly.

TABLE 6 oneM2M Request Parameter List for Multiple filterCriteriaRequest Parameter Criticality Description To Mandatory Address of thetarget resource or target attribute for the operation EW) Note: whenFilterBase present this may be a relative path From Mandatory Identifierrepresenting the Originator Operation Mandatory Operation to beexecuted: Create (C), Retrieve (R), Update (U), Delete (D), Notify (N).Request Identifier Mandatory ID enabling tracking of Requests andcorresponding Responses Content Conditional (C) content of the newresource to be created based on (U) content to be replaced in anexisting resource Operation: (N) notification information MandatoryOptional for: for C, U, N (R) list of attributes to be retrievedOptional for R Resource type Conditional, Resource type for the resourceto be created. Mandatory for C Role Optional Originator role to be usedin role based access control Originating Timestamp Optional Originatingtimestamp of when the message was built. Request Expiration OptionalIndicates when the request messages (including Timestamp delay-tolerant)should expire Response Expiration Optional Indicates when the responsemessages (including Timestamp delay-tolerant) should expire Responsetype Optional Indicates what type of response shall be used. Optionsare: nonBlockingRequestSynch, nonBlockingRequestAsynch, blockingRequestResult Content Optional Indicates what the expected components of theresult are. Options are: attributes, hierarchical- address,hierarchical-address + attributes, attributes + child-resources,child-resources, attributes + child-resource-references, child-resource-references, nothing, original-resource Result PersistenceOptional Indicates the duration for which the address containing theresponses is to persist. Operation Execution Optional Indicates the timewhen the specified operation Time is to be executed by the target CSEEvent Category Optional Indicates the event category that should be usedto handle this request in transit, such as: immediate, bestEffort,latest Delivery Aggregation Optional Enables aggregation of one or morerequest for delivery to the same CSE(s), depending on policies GroupRequest Optional Identifier optionally added to group requests thatIdentifier is to be fanned out, in order to detect loops and avoidduplicated operations. (NEW) Filter Criteria Optional Primary conditionsfor filtered operations. Usage 1 described by Table 5. If empty, nofiltering is used by the Receiver in processing the request. (NEW)Filter Criteria Optional Secondary conditions for filtered operations. 2Usage described by Table 5. If empty, only filtering based on FilterCriteria 1 is used by the Receiver in processing the request. NEW)Filter Criteria 3 Optional Tertiary conditions for filtered operations.Usage described by Table 5. If empty, only filtering based on FilterCriteria 1 and 2 is used by the Receiver in processing the request.Discovery Result Type Optional Indicates the preference of theOriginator for the format of returned information in the result of theoperation. Options are: Hierarchical addressing, non-Hierarchicaladdressing (NEW FilterBase Optional Address of the root where thediscovery begins on Hosting CSE, Choices: FilterCSEBase, Exact URI to beused as filtering base. If not present, no filtering is done.

When Multiple Nested Filter Criteria are used, the Hosting CSE performsstep 0002 of the flow in FIG. 11 as follows:

If (Filter Criteria 1 exists) {  Hosting CSE searches starting from thesearch base FilterBase for all resources meeting FilterCriteria 1, formsFiltering Result 1  If (Filter Criteria 2 exists)  {  Hosting CSEsearches starting from Filtering Result 1 for all resources meetingFilterCriteria 2, forms Filtering Result 2   If (Filter Criteria 3exists)   {   Hosting CSE searches starting from Filtering Result 2 forall  resources meeting FilterCriteria 3, forms Filtering Result 3 == final filtering Result   }  } }

Multiple Filter Criteria Applied at Different Hierarchy Levels

The new parameters for this solution are highlighted in Table 7 alongwith possible modifications and clarifications to be brought to theusage of the existing parameters. In this example we show an example foruse of 3 different filter criteria parameters in the request, two ormore would work similarly.

TABLE 7 oneM2M Request Parameter List for Multiple filterCriteria levelsRequest Parameter Criticality Description To Mandatory Address of thetarget resource or target attribute for the operation (NEW) Note: whenFilterBase present this may be a relative path From Mandatory Identifierrepresenting the Originator Operation Mandatory Operation to beexecuted: Create (C), Retrieve (R), Update (U), Delete (D), Notify (N).Request Identifier Mandatory ID enabling tracking of Requests andcorresponding Responses Content Conditional (C) content of the newresource to be created based on (U) content to be replaced in anexisting resource Operation: (N) notification information Mandatory forOptional for: C, U, N (R) list of attributes to be retrieved Optionalfor R Resource type Conditional, Resource type for the resource to becreated. Mandatory for C Role Optional Originator role to be used inrole based access control Originating Timestamp Optional Originatingtimestamp of when the message was built. Request Expiration OptionalIndicates when the request messages (including Timestamp delay-tolerant)should expire Response Expiration Optional Indicates when the responsemessages (including Timestamp delay-tolerant) should expire Responsetype Optional Indicates what type of response shall be used. Optionsare: nonBlockingRequestSynch, nonBlockingRequestAsynch, blockingRequestResult Content Optional Indicates what the expected components of theresult are. Options are: attributes, hierarchical- address,hierarchical-address + attributes, attributes + child-resources,child-resources, attributes + child-resource-references, child-resource-references, nothing, original-resource Result PersistenceOptional Indicates the duration for which the address containing theresponses is to persist. Operation Execution Optional Indicates the timewhen the specified operation is Time to be executed by the target CSEEvent Category Optional Indicates the event category that should be usedto handle this request in transit, such as: immediate, bestEffort,latest Delivery Aggregation Optional Enables aggregation of one or morerequest for delivery to the same CSE(s), depending on policies GroupRequest Identifier Optional Identifier optionally added to grouprequests that is to be fanned out, in order to detect loops and avoidduplicated operations. (NEW) Optional Conditions for filteredoperations. Usage described BaseFilterCriteria by Table 3 as it appliesto FilterBase. If empty, no filtering is used by the Receiver inprocessing the request. (NEW) Optional Conditions for filteredoperations. Usage described ChildFilterCriteria by Table 3 as it appliesto the children of the resources matched by BaseFilterCriteria. Ifempty, only filtering based on BaseFilterCriteria and, if present,ParentFilterCriteria is used by the Receiver in processing the request.(NEW) Optional Conditions for filtered operations. Usage describedParentFilterCriteria by Table 3 as it applies to the parents of theresources matched by BaseFilterCriteria. If empty, only filtering basedon BaseFilterCriteria and, if present, ChildFilterCriteria is used bythe Receiver in processing the request. Discovery Result Type OptionalIndicates the preference of the Originator for the format of returnedinformation in the result of the operation. Options are: Hierarchicaladdressing, non-Hierarchical addressing (NEW) FilterBase OptionalAddress of the root where the discovery begins on Hosting CSE, Choices:FilterCSEBase, Extract URI to be used as a filtering base. If notpresent no filtering is done.

When Multiple Level Filter Criteria are used, the Hosting CSE performsstep 0002 of the flow in FIG. 11 as follows:

If (BaseFilterCriteria NOT NULL) {  Hosting CSE searches starting fromthe search base FilterBase  While (Resource X meets BaseFilterCriteria) {   If ( (ChildFilterCriteria NOT NULL) AND (child Y of resource X  meets ChildFilterCriteria) )   OR (ChildFilterCriteria == NULL)   {  If ( (ParentFilterCriteria NOT NULL) AND (Parent Z of resource   Xmeets ParentFilterCriteria) )   OR (ParentFilterCriteria == NULL)    {   Resource X = matchCandidate    Hosting CSE adds Resource X toFiltering Result    }   }  } do search through the tree }

Additional Filter Criteria Search Parameters

The parameters of Table 8 may be used in addition to those discussedabove.

TABLE 8 Additional FilterCriteria Search Parameter Resource matching if:(NEW) The Matched Resource is a container whose latestlatestCreatedBefore <contentInstance> was created before createdBefore(NEW) latestCreatedAfter The Matched Resource is a container whoselatest <contentInstance> was created before createdAfter (NEW)latestModifiedSince The Matched Resource is a container whose latest<contentInstance> was created before modifiedSince (NEW) The MatchedResource is a container whose latest latestUnmodifiedSince<contentInstance> was created before unmodifiedSince (NEW) The MatchedResource is a container whose latest latestStateTagSmaller<contentInstance> has stateTag attribute smaller than stateTagSmaller(NEW) The Matched Resource is a container whose latestlatestStateTagBigger <contentInstance> has stateTag larger thanStateTagBigger (NEW) latestSizeAbove The Matched Resource is a containerwhose latest <contentInstance> has contentSize attribute equal to orgreater than the sizeAbove value (NEW) latestSizeBelow The MatchedResource is a container whose latest <contentInstance> has contentSizeattribute smaller than the sizeBelow value (NEW) latestContentType TheMatched Resource is a container whose latest <contentInstance> hascontentInfo attribute that matches the contentType value (NEW) TheMatched Resource is a container whose oldest oldestCreatedBefore<contentInstance> was created before createdBefore (NEW)oldestCreatedAfter The Matched Resource is a container whose oldest<contentInstance> was created before createdAfter (NEW) The MatchedResource is a container whose oldest oldestModifiedSince<contentInstance> was modified since modifiedSince (NEW) The MatchedResource is a container whose oldest oldestUnmodifiedSince<contentInstance> was unmodified since unmodifiedSince NEW) The MatchedResource is a container whose oldest oldestStateTagSmaller<contentInstance> has stateTag attribute smaller than stateTagSmallerNEW) The Matched Resource is a container whose oldestoldestStateTagBigger <contentInstance> has stateTag attribute largerthan stateTagBigger (NEW) oldestSizeAbove The Matched Resource is acontainer whose latest <contentInstance> has contentSize attribute equalto or greater than the sizeAbove value (NEW) oldestSizeBelow The MatchedResource is a container whose latest <contentInstance> has contentSizeattribute smaller the sizeBelow value (NEW) oldestContentType TheMatched Resource is a container whose oldest <contentInstance> hascontentInfo attribute that matches the contentType value (NEW) TheMatched Resource has to have as a parent a resource parentCreatedBeforecreated before the given time value. (NEW) parentCreatedAfter TheMatched Resource has to have as a parent a resource created after thegiven time value. (NEW) The Matched Resource has to have as a parent aresource parentModifiedSince modified since the given time value. (NEW)The Matched Resource has to have as a parent a resourceparentUnmodifiedSince unmodified since the given time value. (NEW)parentTagSmaller The Matched Resource has to have as a parent resourcewith a StateTag smaller than the given value. (NEW) parentTagBigger TheMatched Resource has to have as a parent resource with a StateTag largerthan the given value. (NEW) childCreatedBefore The Matched Resource hasto have as a child a resource created before the given time value. (NEW)childCreatedAfter The Matched Resource has to have as a child a resourcecreated after the given time value. (NEW) childModifiedSince The MatchedResource has to have as a child a resource modified since the given timevalue (NEW) The Matched Resource has to have as a child a resourcechildUnmodifiedSince unmodified since the given time value (NEW) TheMatched Resource has to have as a child a resource withchildStateTagSmaller a StateTag smaller than the given value. (NEW) TheMatched Resource has to have as a child a resource withchildStateTagBigger a StateTag larger than the given value.

User Interface

Interfaces, such as Graphical User Interfaces (GUIs), can be used toassist user to control and/or configure functionalities related toEnhanced RESTful operations. FIG. 13 is a diagram that illustrates aninterface 1302. Enhanced RESTful operations may be enabled by a user orapplication to improve communication efficiency, and some of theparameters, listed in Table 4, Table 5, Table 6, Table 7 and Table 8,may also be pre-configured by a user or application for default valuesas shown in interface 1302.It is to be understood that interface 1302can be produced using displays such as those shown in FIGS. 14C-Ddescribed below.

Example M2M/IoT/WoT Communication System

The various techniques described herein may be implemented in connectionwith hardware, firmware, software or, where appropriate, combinationsthereof. Such hardware, firmware, and software may reside in apparatuseslocated at various nodes of a communication network. The apparatuses mayoperate singly or in combination with each other to effect the methodsdescribed herein. As used herein, the terms “apparatus,” “networkapparatus,” “node,” “device,” and “network node” may be usedinterchangeably.

The service layer may be a functional layer within a network servicearchitecture. Service layers are typically situated above theapplication protocol layer such as HTTP, CoAP or MQTT and provide valueadded services to client applications. The service layer also providesan interface to core networks at a lower resource layer, such as forexample, a control layer and transport/access layer. The service layersupports multiple categories of (service) capabilities orfunctionalities including a service definition, service runtimeenablement, policy management, access control, and service clustering.Recently, several industry standards bodies, e.g., oneM2M, have beendeveloping M2M service layers to address the challenges associated withthe integration of M2M types of devices and applications intodeployments such as the Internet/Web, cellular, enterprise, and homenetworks. A M2M service layer can provide applications and/or variousdevices with access to a collection of or a set of the above mentionedcapabilities or functionalities, supported by the service layer, whichcan be referred to as a CSE or SCL. A few examples include but are notlimited to security, charging, data management, device management,discovery, provisioning, and connectivity management which can becommonly used by various applications. These capabilities orfunctionalities are made available to such various applications via APIswhich make use of message formats, resource structures and resourcerepresentations defined by the M2M service layer. The CSE or SCL is afunctional entity that may be implemented by hardware and/or softwareand that provides (service) capabilities or functionalities exposed tovarious applications and/or devices (i.e., functional interfaces betweensuch functional entities) in order for them to use such capabilities orfunctionalities.

FIG. 14A is a diagram of an example machine-to machine (M2M), Internetof Things (IoT), or Web of Things (WoT) communication system 10 in whichone or more disclosed embodiments may be implemented. Generally, M2Mtechnologies provide building blocks for the IoT/WoT, and any M2Mdevice, M2M gateway, M2M server, or M2M service platform may be acomponent or node of the IoT/WoT as well as an IoT/WoT service layer,etc. Communication system 10 can be used to implement functionality ofthe disclosed embodiments and can include functionality and logicalentities such as originator 402, receiver 404, receiver CSE 404′, AE_tm604, MN-CSE1 602 and logical entities to produce interfaces such asinterface 1302.

As shown in FIG. 14A, the M2M/IoT/WoT communication system 10 includes acommunication network 12. The communication network 12 may be a fixednetwork (e.g., Ethernet, Fiber, TSDN, PLC, or the like) or a wirelessnetwork (e.g., WLAN, cellular, or the like) or a network ofheterogeneous networks. For example, the communication network 12 may becomprised of multiple access networks that provide content such asvoice, data, video, messaging, broadcast, or the like to multiple users.For example, the communication network 2 may employ one or more channelaccess methods, such as code division multiple access (CDMA), timedivision multiple access (TDMA), frequency division multiple access(FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), and thelike. Further, the communication network 2 may comprise other networkssuch as a core network, the Internet, a sensor network, an industrialcontrol network, a personal area network, a fused personal network, asatellite network, a home network, or an enterprise network for example.

As shown in FIG. 14A, the M2M/ IoT/WoT communication system 10 mayinclude the Infrastructure Domain and the Field Domain. TheInfrastructure Domain refers to the network side of the end-to-end M2Mdeployment, and the Field Domain refers to the area networks, usuallybehind an M2M gateway. The Field Domain and Infrastructure Domain mayboth comprise a variety of different network nodes (e.g., servers,gateways, device, and the like). For example, the Field Domain mayinclude M2M gateways 14 and terminal devices 18. It will be appreciatedthat any number of M2M gateway devices 14 and M2M terminal devices 18may be included in the M2M/ IoT/WoT communication system 10 as desired.Each of the M2M gateway devices 14 and M2M terminal devices 18 areconfigured to transmit and receive signals, using communicationscircuitry, via the communication network 2 or direct radio link. A M2Mgateway 14 allows wireless M2M devices (e.g. cellular and non-cellular)as well as fixed network M2M devices (e.g., PLC) to communicate eitherthrough operator networks, such as the communication network 2 or directradio link. For example, the M2M terminal devices 18 may collect dataand send the data, via the communication network 2 or direct radio link,to an M2M application 20 or other M2M devices 18. The M2M terminaldevices 18 may also receive data from the M2M application 20 or an M2Mterminal device 18. Further, data and signals may be sent to andreceived from the M2M application 20 via an M2M service layer 22, asdescribed below. M2M terminal devices 18 and gateways 14 may communicatevia various networks including, cellular, WLAN, WPAN (e.g., Zigbee,6LoWPAN, Bluetooth), direct radio link, and wireline for example.

Exemplary M2M terminal devices 18 include, but are not limited to,tablets, smart phones, medical devices, temperature and weathermonitors, connected cars, smart meters, game consoles, personal digitalassistants, health and fitness monitors, lights, thermostats,appliances, garage doors and other actuator-based devices, securitydevices, and smart outlets.

Referring to FIG. 14B, the illustrated M2M service layer 22 in the fielddomain provides services for the M2M application 20, M2M gateway devices14, and M2M terminal devices 18 and the communication network 12.Communication network 2 can be used to implement functionality of thedisclosed embodiments and can include functionality and logical entitiessuch as originator 402, receiver 404, receiver CSE 404′, AE_tm 604,MN-CSE1 602 and logical entities to produce interfaces such as interface1302. The M2M service layer 22 may be implemented by one or moreservers, computers, devices, virtual machines (e.g. cloud/ storagefarms, etc.) or the like, including for example the devices illustratedin FIGS. 14C and 14D described below. It will be understood that the M2Mservice layer 22 may communicate with any number of M2M applications,M2M gateways 14, M2M terminal devices 18, and communication networks 12as desired. The M2M service layer 22 may be implemented by one or morenodes of the network, which may comprises servers, computers, devices,or the like. The M2M service layer 22 provides service capabilities thatapply to M2M terminal devices 18, M2M gateways 14, and M2M applications20. The functions of the M2M service layer 22 may be implemented in avariety of ways, for example as a web server, in the cellular corenetwork, in the cloud, etc.

Similar to the illustrated M2M service layer 22, there is the M2Mservice layer 22′ in the Infrastructure Domain. M2M service layer 22′provides services for the M2M application 20′ and the underlyingcommunication network 2 in the infrastructure domain. M2M service layer22′ also provides services for the M2M gateways 14 and M2M terminaldevices 18 in the field domain. It will be understood that the M2Mservice layer 22′ may communicate with any number of M2M applications,M2M gateways and M2M devices. The M2M service layer 22′ may interactwith a service layer by a different service provider. The M2M servicelayer 22′ by one or more nodes of the network, which may comprisesservers, computers, devices, virtual machines (e.g., cloudcomputing/storage farms, etc.) or the like.

Referring also to FIG. 14B, the M2M service layers 22 and 22′ provide acore set of service delivery capabilities that diverse applications andverticals can leverage. These service capabilities enable M2Mapplications 20 and 20′ to interact with devices and perform functionssuch as data collection, data analysis, device management, security,billing, service/device discovery etc. Essentially, these servicecapabilities free the applications of the burden of implementing thesefunctionalities, thus simplifying application development and reducingcost and time to market. The service layers 22 and 22′ also enable M2Mapplications 20 and 20′ to communicate through networks 12 in connectionwith the services that the service layers 22 and 22′ provide.

The methods of the present application may be implemented as part of aservice layer 22 and 22′. The service layer 22 and 22′ is a softwaremiddleware layer that supports value-added service capabilities througha set of Application Programming Interfaces (APIs) and underlyingnetworking interfaces. Both ETSI M2M and oneM2M use a service layer thatmay contain the connection methods of the present application. ETSIM2M′s service layer is referred to as the Service Capability Layer (SCL). The SCL may be implemented within an M2M device (where it is referredto as a device SCL (DSCL)), a gateway (where it is referred to as agateway SCL (GSCL)) and/or a network node (where it is referred to as anetwork SCL (NSCL)). The oneM2M service layer supports a set of CommonService Functions (CSFs) (i.e. service capabilities). An instantiationof a set of one or more particular types of CSFs is referred to as aCommon Services Entity (CSE) which can be hosted on different types ofnetwork nodes (e.g. infrastructure node, middle node,application-specific node). Further, connection methods of the presentapplication can implemented as part of an M2M network that uses aService Oriented Architecture (SOA) and/or a resource-orientedarchitecture (ROA) to access services such as the connection methods ofthe present application.

In some embodiments, M2M applications 20 and 20′ may be used inconjunction with the disclosed systems and methods.. The M2Mapplications 20 and 20′ may include the applications that interact withthe UE or gateway and may also be used in conjunction with otherdisclosed systems and methods.

In one embodiment, the logical entities such as originator 402, receiver404, receiver CSE 404′, AE_tm 604, MN-CSE1 602 and logical entities toproduce interfaces such as interface 1302 may be hosted within a M2Mservice layer instance hosted by an M2M node, such as an M2M server, M2Mgateway, or M2M device, as shown in FIG. 14B. For example, the logicalentities such as originator 402, receiver 404, receiver CSE 404′, AE_tm604, MN-CSE1 602 and logical entities to produce interfaces such asinterface 1302 may comprise an individual service capability within theM2M service layer instance or as a sub-function within an existingservice capability.

In describing preferred embodiments of the subject matter of the presentdisclosure, as illustrated in the Figures, specific terminology isemployed for the sake of clarity. The claimed subject matter, however,is not intended to be limited to the specific terminology so selected,and it is to be understood that each specific element includes alltechnical equivalents that operate in a similar manner to accomplish asimilar purpose.

The M2M applications 20 and 20′ may include applications in variousindustries such as, without limitation, transportation, health andwellness, connected home, energy management, asset tracking, andsecurity and surveillance. As mentioned above, the M2M service layer,running across the devices, gateways, servers and other nodes of thesystem, supports functions such as, for example, data collection, devicemanagement, security, billing, location tracking/geofencing,device/service discovery, and legacy systems integration, and providesthese functions as services to the M2M applications 20 and 20′.

Generally, the service layers 22 and 22′ define a software middlewarelayer that supports value-added service capabilities through a set ofApplication Programming Interfaces (APIs) and underlying networkinginterfaces. Both the ETSI M2M and oneM2M architectures define a servicelayer. ETSI M2M′s service layer is referred to as the Service CapabilityLayer (SCL). The SCL may be implemented in a variety of different nodesof the ETSI M2M architecture. For example, an instance of the servicelayer may be implemented within an M2M device (where it is referred toas a device SCL (DSCL)), a gateway (where it is referred to as a gatewaySCL (GSCL)) and/or a network node (where it is referred to as a networkSCL (NSCL)). The oneM2M service layer supports a set of Common ServiceFunctions (CSFs) (i.e., service capabilities). An instantiation of a setof one or more particular types of CSFs is referred to as a CommonServices Entity (CSE) which can be hosted on different types of networknodes (e.g. infrastructure node, middle node, application-specificnode). The Third Generation Partnership Project (3GPP) has also definedan architecture for machine-type communications (MTC). In thatarchitecture, the service layer, and the service capabilities itprovides, are implemented as part of a Service Capability Server (SCS).Whether embodied in a DSCL, GSCL, or NSCL of the ETSI M2M architecture,in a Service Capability Server (SCS) of the 3GPP MTC architecture, in aCSF or CSE of the oneM2M architecture, or in some other node of anetwork, an instance of the service layer may be implemented as alogical entity (e.g., software, computer-executable instructions, andthe like) executing either on one or more standalone nodes in thenetwork, including servers, computers, and other computing devices ornodes, or as part of one or more existing nodes. As an example, aninstance of a service layer or component thereof may be implemented inthe form of software running on a network node (e.g., server, computer,gateway, device or the like) having the general architecture illustratedin FIG. 14C or FIG. 14D described below.

Further, logical entities such as originator 402, receiver 404, receiverCSE 404′, AE_tm 604, MN-CSE1 602 and logical entities to produceinterfaces such as interface 1302 can implemented as part of an M2Mnetwork that uses a Service Oriented Architecture (SOA) and/or aResource-Oriented Architecture (ROA) to access services of the presentapplication.

FIG. 14C is a block diagram of an example hardware/software architectureof a M2M network node 30, such as an M2M device 18, an M2M gateway 14,an M2M server, or the like. The node 30 can execute or include logicalentities such as originator 402, receiver 404, receiver CSE 404′, AE_tm604, MN-CSE1 602 and logical entities to produce interfaces such asinterface 1302. The device 30 can be part of an M2M network as shown inFIG. 14A-B or part of a non-M2M network. As shown in FIG. 14C, the M2Mnode 30 may include a processor 32, non-removable memory 44, removablememory 46, a speaker/microphone 38, a keypad 40, a display, touchpad,and/or indicators 42, a power source 48, a global positioning system (GPS) chipset 50, and other peripherals 52. The node 30 may also includecommunication circuitry, such as a transceiver 34 and a transmit/receiveelement 36. It will be appreciated that the M2M node 30 may include anysub-combination of the foregoing elements while remaining consistentwith an embodiment. This node may be a node that implements the SMSFfunctionality described herein.

The processor 32 may be a general purpose processor, a special purposeprocessor, a conventional processor, a digital signal processor (DSP), aplurality of microprocessors, one or more microprocessors in associationwith a DSP core, a controller, a microcontroller, Application SpecificIntegrated Circuits (ASICs), Field Programmable Gate Array (FPGAs)circuits, any other type of integrated circuit (IC), a state machine,and the like. In general, the processor 32 may executecomputer-executable instructions stored in the memory (e.g., memory 44and/or memory 46) of the node in order to perform the various requiredfunctions of the node. For example, the processor 32 may perform signalcoding, data processing, power control, input/output processing, and/orany other functionality that enables the M2M node 30 to operate in awireless or wired environment. The processor 32 may runapplication-layer programs (e.g., browsers) and/or radio access-layer(RAN) programs and/or other communications programs. The processor 32may also perform security operations such as authentication, securitykey agreement, and/or cryptographic operations, such as at theaccess-layer and/or application layer for example.

As shown in FIG. 14C, the processor 32 is coupled to its communicationcircuitry (e.g., transceiver 34 and transmit/receive element 36). Theprocessor 32, through the execution of computer executable instructions,may control the communication circuitry in order to cause the node 30 tocommunicate with other nodes via the network to which it is connected.In particular, the processor 32 may control the communication circuitryin order to perform the transmitting and receiving steps describedherein and in the claims. While FIG. 14C depicts the processor 32 andthe transceiver 34 as separate components, it will be appreciated thatthe processor 32 and the transceiver 34 may be integrated together in anelectronic package or chip.

The transmit/receive element 36 may be configured to transmit signalsto, or receive signals from, other M2M nodes, including M2M servers,gateways, device, and the like. For example, in an embodiment, thetransmit/receive element 36 may be an antenna configured to transmitand/or receive RF signals. The transmit/receive element 36 may supportvarious networks and air interfaces, such as WLAN, WPAN, cellular, andthe like. In an embodiment, the transmit/receive element 36 may be anemitter/detector configured to transmit and/or receive IR, UV, orvisible light signals, for example. In yet another embodiment, thetransmit/receive element 36 may be configured to transmit and receiveboth RF and light signals. It will be appreciated that thetransmit/receive element 36 may be configured to transmit and/or receiveany combination of wireless or wired signals.

In addition, although the transmit/receive element 36 is depicted inFIG. 14C as a single element, the M2M node 30 may include any number oftransmit/receive elements 36. More specifically, the M2M node 30 mayemploy MIMO technology. Thus, in an embodiment, the M2M node 30 mayinclude two or more transmit/receive elements 36 (e.g., multipleantennas) for transmitting and receiving wireless signals.

The transceiver 34 may be configured to modulate the signals that are tobe transmitted by the transmit/receive element 36 and to demodulate thesignals that are received by the transmit/receive element 36. As notedabove, the M2M node 30 may have multi-mode capabilities. Thus, thetransceiver 34 may include multiple transceivers for enabling the M2Mnode 30 to communicate via multiple RATS, such as UTRA and IEEE 802.11,for example.

The processor 32 may access information from, and store data in, anytype of suitable memory, such as the non-removable memory 44 and/or theremovable memory 46. For example, the processor 32 may store sessioncontext in its memory, as described above. The non-removable memory 44may include random-access memory (RAM), read-only memory (ROM), a harddisk, or any other type of memory storage device. The removable memory46 may include a subscriber identity module (SIM) card, a memory stick,a secure digital (SD) memory card, and the like. In other embodiments,the processor 32 may access information from, and store data in, memorythat is not physically located on the M2M node 30, such as on a serveror a home computer. The processor 32 may be configured to controllighting patterns, images, or colors on the display or indicators 42 toreflect the status of an M2M service layer session migration or sharingor to obtain input from a user or display information to a user aboutthe node's session migration or sharing capabilities or settings. Inanother example, the display may show information with regard to asession state. The current disclosure defines a RESTful user/applicationAPI in the oneM2M embodiment. A graphical user interface, which may beshown on the display, may be layered on top of the API to allow a userto interactively establish and manage an E2E session, or the migrationor sharing thereof, via the underlying service layer sessionfunctionality described herein.

The processor 32 may receive power from the power source 48, and may beconfigured to distribute and/or control the power to the othercomponents in the M2M node 30. The power source 48 may be any suitabledevice for powering the M2M node 30. For example, the power source 48may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd),nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion),etc.), solar cells, fuel cells, and the like.

The processor 32 may also be coupled to the GPS chipset 50, which isconfigured to provide location information (e.g., longitude andlatitude) regarding the current location of the M2M node 30. It will beappreciated that the M2M node 30 may acquire location information by wayof any suitable location-determination method while remaining consistentwith an embodiment.

The processor 32 may further be coupled to other peripherals 52, whichmay include one or more software and/or hardware modules that provideadditional features, functionality and/or wired or wirelessconnectivity. For example, the peripherals 52 may include varioussensors such as an accelerometer, biometrics (e.g., fingerprint)sensors, an e-compass, a satellite transceiver, a digital camera (forphotographs or video), a universal serial bus (USB) port or otherinterconnect interfaces, a vibration device, a television transceiver, ahands free headset, a Bluetooth® module, a frequency modulated (FM)radio unit, a digital music player, a media player, a video game playermodule, an Internet browser, and the like.

The node 30 may be embodied in other apparatuses or devices, such as asensor, consumer electronics, a wearable device such as a smart watch orsmart clothing, a medical or eHealth device, a robot, industrialequipment, a drone, a vehicle such as a car, truck, train, or airplane.The node 30 may connect to other components, modules, or systems of suchapparatuses or devices via one or more interconnect interfaces, such asan interconnect interface that may comprise one of the peripherals 52.Alternately, the node 30 may comprise apparatuses or devices, such as asensor, consumer electronics, a wearable device such as a smart watch orsmart clothing, a medical or eHealth device, a robot, industrialequipment, a drone, a vehicle such as a car, truck, train, or airplane.

FIG. 14D is a block diagram of an exemplary computing system 90 whichmay also be used to implement one or more nodes of an M2M network, suchas an M2M server, gateway, device, or other node. Computing system 90may comprise a computer or server and may be controlled primarily bycomputer readable instructions, which may be in the form of software,wherever, or by whatever means such software is stored or accessed.Computing system 90 can execute or include logical entities such asoriginator 402, receiver 404, receiver CSE 404′, AE_tm 604, MN-CSE1 602and logical entities to produce interfaces such as interface 1302.Computing system 90 can be an M2M device, user equipment, gateway, UE/GWor any other nodes including nodes of the mobile care network, servicelayer network application provider, terminal device 18 or an M2M gatewaydevice 14 for example. Such computer readable instructions may beexecuted within a processor, such as central processing unit (CPU) 91,to cause computing system 90 to do work. In many known workstations,servers, and personal computers, central processing unit 91 isimplemented by a single-chip CPU called a microprocessor. In othermachines, the central processing unit 91 may comprise multipleprocessors. Coprocessor 81 is an optional processor, distinct from mainCPU 91, that performs additional functions or assists CPU 91. CPU 91and/or coprocessor 81 may receive, generate, and process data related tothe disclosed systems and methods for E2E M2M service layer sessions,such as receiving session credentials or authenticating based on sessioncredentials.

In operation, CPU 91 fetches, decodes, and executes instructions, andtransfers information to and from other resources via the computer'smain data-transfer path, system bus 80. Such a system bus connects thecomponents in computing system 90 and defines the medium for dataexchange. System bus 80 typically includes data lines for sending data,address lines for sending addresses, and control lines for sendinginterrupts and for operating the system bus. An example of such a systembus 80 is the PCI (Peripheral Component Interconnect) bus.

Memories coupled to system bus 80 include random access memory (RAM) 82and read only memory (ROM) 93. Such memories include circuitry thatallows information to be stored and retrieved. ROMs 93 generally containstored data that cannot easily be modified. Data stored in RAM 82 can beread or changed by CPU 91 or other hardware devices. Access to RAM 82and/or ROM 93 may be controlled by memory controller 92. Memorycontroller 92 may provide an address translation function thattranslates virtual addresses into physical addresses as instructions areexecuted. Memory controller 92 may also provide a memory protectionfunction that isolates processes within the system and isolates systemprocesses from user processes. Thus, a program running in a first modecan access only memory mapped by its own process virtual address space;it cannot access memory within another process's virtual address spaceunless memory sharing between the processes has been set up.

In addition, computing system 90 may contain peripherals controller 83responsible for communicating instructions from CPU 91 to peripherals,such as printer 94, keyboard 84, mouse 95, and disk drive 85.

Display 86, which is controlled by display controller 96, is used todisplay visual output generated by computing system 90. Such visualoutput may include text, graphics, animated graphics, and video. Display86 may be implemented with a CRT-based video display, an LCD-basedflat-panel display, gas plasma-based flat-panel display, or atouch-panel. Display controller 96 includes electronic componentsrequired to generate a video signal that is sent to display 86.

Further, computing system 90 may contain communication circuitry, suchas for example a network adaptor 97, that may be used to connectcomputing system 90 to an external communications network, such asnetwork 2 of FIG. 14A and FIG. 14B, to enable the computing system 90 tocommunicate with other nodes of the network.

User equipment (UE) can be any device used by an end-user tocommunicate. It can be a hand-held telephone, a laptop computer equippedwith a mobile broadband adapter, or any other device. For example, theUE can be implemented as the M2M terminal device 18 of FIGS. 14 A-B orthe device 30 of FIG. 14C.

It is understood that any or all of the systems, methods, and processesdescribed herein may be embodied in the form of computer executableinstructions (i.e., program code) stored on a computer-readable storagemedium which instructions, when executed by a machine, such as a node ofan M2M network, including for example an M2M server, gateway, device orthe like, perform and/or implement the systems, methods and processesdescribed herein. Specifically, any of the steps, operations orfunctions described above, including the operations of the gateway, UE,UE/GW, or any of the nodes of the mobile core network, service layer ornetwork application provider, may be implemented in the form of suchcomputer executable instructions. Logical entities such as originator402, receiver 404, receiver CSE 404′, AE_tm 604, MN-CSE1 602 and logicalentities to produce interfaces such as interface 1302 may be embodied inthe form of the computer executable instructions stored on acomputer-readable storage medium. Computer readable storage mediainclude both volatile and nonvolatile, removable and non-removable mediaimplemented in any non-transitory (i.e., tangible or physical) method ortechnology for storage of information, but such computer readablestorage media do not includes signals. Computer readable storage mediainclude, but are not limited to, RAM, ROM, EEPROM, flash memory or othermemory technology, CD-ROM, digital versatile disks (DVD) or otheroptical disk storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other tangible orphysical medium which can be used to store the desired information andwhich can be accessed by a computer.

This written description uses examples to disclose the invention,including the best mode, and also to enable any person skilled in theart to practice the invention, including making and using any devices orsystems and performing any incorporated methods. The patentable scope ofthe invention is defined by the claims, and may include other examplesthat occur to those skilled in the art. Such other examples are intendedto be within the scope of the claims if they have elements that do notdiffer from the literal language of the claims, or if they includeequivalent elements with insubstantial differences from the literallanguage of the claims.

What is claimed:
 1. An apparatus comprising a processor and a memory,the apparatus further including computer-executable instructions storedin the memory of the apparatus which, when executed by the processor ofthe apparatus, cause the apparatus to: receive a request that indicatesa resource discovery operation with associated filter criteria and alsoindicates a RESTful operation with associated operation parameters,wherein the resource discovery operation comprises a request for aresult resource set comprising one or more resources matching theassociated filter criteria, and wherein the RESTful operation is to beperformed in accordance with the associated operation parameters on atarget resource set comprising one or more resources related to theresult resource set; determine the result resource set, as indicated bythe request; determine the target resource set, as indicated by therequest; and perform the RESTful operation on the target resource set,as indicated by the request.
 2. The apparatus of claim 1, wherein thetarget resource set is identical to the result resource set and theRESTful operation is performed on the result resource set resulting fromthe resource discovery operation.
 3. The apparatus of claim 1, whereinthe computer-executable instructions, when executed, further cause theapparatus to send a response that indicates that the RESTful operationwas performed.
 4. The apparatus of claim 1 wherein the request furtherindicates the creation of a group from the result resource set matchingthe associated filter criteria.
 5. The apparatus of claim 1, wherein therequest indicates that the RESTful operation is to be performed on atarget resource set related to but different from the result resourceset of the resource discovery operation.
 6. The apparatus of claim 1,wherein the request further comprises a root resource on which toperform the resource discovery operation that is not included in thetarget resource set.
 7. The apparatus of claim 1, wherein the requestfurther comprises a resource relationship parameter indicating a type ofrelationship between resources, and wherein the target resource setcomprises one or more resources related to the one or more resources ofthe result resource set by the type of relationship indicated by theresource relationship parameter.
 8. The apparatus of claim 7, whereinthe resource relationship parameter indicates a parent type ofrelationship.
 9. The apparatus of claim 7, wherein the resourcerelationship parameter indicates a semantic type of relationship,wherein a semantic type of relationship between a first resource and asecond resource comprises the first resource containing semanticinformation for the second resource.
 10. The apparatus of claim 7,wherein the resource relationship parameter indicates a subscriptiontype of relationship, wherein a subscription type of relationshipbetween a first resource and a second resource comprises the firstresource containing subscription information for the second resource.11. A method comprising: receiving a request that indicates a resourcediscovery operation with associated filter criteria and also indicates aRESTful operation with associated operation parameters, wherein theresource discovery operation comprises a request for a result resourceset comprising one or more resources matching the associated filtercriteria, and wherein the RESTful operation is to be performed inaccordance with the associated operation parameters on a target resourceset comprising one or more resources related to the result resource set;determining the result resource set, as indicated by the request;determining the target resource set, as indicated by the request; andperform the RESTful operation on the target resource set, as indicatedby the request.
 12. The method of claim 11, wherein the target resourceset is identical to the result resource set and the RESTful operation isperformed on the result resource set resulting from the resourcediscovery operation.
 13. The method of claim 11, further comprisingsending a response that indicates that the RESTful operation wasperformed.
 14. The method of claim 11 wherein the request furtherindicates the creation of a group from the result resource set matchingthe associated filter criteria.
 15. The method of claim 11, wherein therequest indicates that the RESTful operation is to be performed on atarget resource set related to but different from the result resourceset of the resource discovery operation.
 16. The method of claim 11,wherein the request further comprises a root resource to perform theresource discovery operation on that is not included in the targetresource set.
 17. The method of claim 11, wherein the request furthercomprises a resource relationship parameter indicating a type ofrelationship between resources, and wherein the target resource setcomprises one or more resources related to the one or more resources ofthe result resource set by the type of relationship indicated by theresource relationship parameter.
 18. The method of claim 17, wherein theresource relationship parameter indicates a parent type of relationship.19. The method of claim 17, wherein the resource relationship parameterindicates a semantic type of relationship, wherein a semantic type ofrelationship between a first resource and a second resource comprisesthe first resource containing semantic information for the secondresource.
 20. The method of claim 17, wherein the resource relationshipparameter indicates a subscription type of relationship, wherein asubscription type of relationship between a first resource and a secondresource comprises the first resource containing subscriptioninformation for the second resource.